Rechercher dans le manuel MySQL

22.6.7 Using Two Replication Channels for NDB Cluster Replication

Contents

In a more complete example scenario, we envision two replication channels to provide redundancy and thereby guard against possible failure of a single replication channel. This requires a total of four replication servers, two masters for the master cluster and two slave servers for the slave cluster. For purposes of the discussion that follows, we assume that unique identifiers are assigned as shown here:

Table 22.425 NDB Cluster replication servers described in the text

Server ID Description
1 Master - primary replication channel (M)
2 Master - secondary replication channel (M')
3 Slave - primary replication channel (S)
4 Slave - secondary replication channel (S')

Setting up replication with two channels is not radically different from setting up a single replication channel. First, the mysqld processes for the primary and secondary replication masters must be started, followed by those for the primary and secondary slaves. Then the replication processes may be initiated by issuing the START SLAVE statement on each of the slaves. The commands and the order in which they need to be issued are shown here:

  1. Start the primary replication master: 

    shellM> mysqld --ndbcluster --server-id=1 \
               --log-bin &

  2. Start the secondary replication master: 

    shellM'> mysqld --ndbcluster --server-id=2 \
               --log-bin &

  3. Start the primary replication slave server: 

    shellS> mysqld --ndbcluster --server-id=3 \
               --skip-slave-start &

  4. Start the secondary replication slave: 

    shellS'> mysqld --ndbcluster --server-id=4 \
                --skip-slave-start &

  5. Finally, initiate replication on the primary channel by executing the START SLAVE statement on the primary slave as shown here:

    1. mysqlS> START SLAVE;
    Warning

    Only the primary channel is to be started at this point. The secondary replication channel is to be started only in the event that the primary replication channel fails, as described in Section 22.6.8, “Implementing Failover with NDB Cluster Replication”. Running multiple replication channels simultaneously can result in unwanted duplicate records being created on the replication slaves.

As mentioned previously, it is not necessary to enable binary logging on replication slaves.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en//mysql-rf-mysql-cluster-replication-two-channels.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut