21.7.5 Preparing the NDB Cluster for Replication (original) (raw)

21.7.5 Preparing the NDB Cluster for Replication

Preparing the NDB Cluster for replication consists of the following steps:

  1. Check all MySQL servers for version compatibility (seeSection 21.7.2, “General Requirements for NDB Cluster Replication”).
  2. Create a replication account on the source Cluster with the appropriate privileges, using the following two SQL statements:
mysqlS> CREATE USER 'replica_user'@'replica_host'  
     -> IDENTIFIED BY 'replica_password';  
mysqlS> GRANT REPLICATION SLAVE ON *.*  
     -> TO 'replica_user'@'replica_host';

In the previous statement,replicauser is the replication account user name, replicahost is the host name or IP address of the replica, and_replicapassword_ is the password to assign to this account.
For example, to create a replica user account with the namemyreplica, logging in from the host namedreplica-host, and using the password53cr37, use the followingCREATE USER andGRANT statements: 

mysqlS> CREATE USER 'myreplica'@'replica-host'  
     -> IDENTIFIED BY '53cr37';  
mysqlS> GRANT REPLICATION SLAVE ON *.*  
     -> TO 'myreplica'@'replica-host';

For security reasons, it is preferable to use a unique user account—not employed for any other purpose—for the replication account. 3. Set up the replica to use the source. Using themysql client, this can be accomplished with the following CHANGE MASTER TO statement: 

mysqlR> CHANGE MASTER TO  
     -> MASTER_HOST='source_host',  
     -> MASTER_PORT=source_port,  
     -> MASTER_USER='replica_user',  
     -> MASTER_PASSWORD='replica_password';

In the previous statement,sourcehost is the host name or IP address of the replication source,sourceport is the port for the replica to use when connecting to the source,replicauser is the user name set up for the replica on the source, and_replicapassword_ is the password set for that user account in the previous step.
For example, to tell the replica to use the MySQL server whose host name is rep-source with the replication account created in the previous step, use the following statement: 

mysqlR> CHANGE MASTER TO  
     -> MASTER_HOST='rep-source',  
     -> MASTER_PORT=3306,  
     -> MASTER_USER='myreplica',  
     -> MASTER_PASSWORD='53cr37';

For a complete list of options that can be used with this statement, see Section 13.4.2.1, “CHANGE MASTER TO Statement”.
To provide replication backup capability, you also need to add an --ndb-connectstring option to the replica's my.cnf file prior to starting the replication process. SeeSection 21.7.9, “NDB Cluster Backups With NDB Cluster Replication”, for details.
For additional options that can be set inmy.cnf for replicas, seeSection 16.1.6, “Replication and Binary Logging Options and Variables”. 4. If the source cluster is already in use, you can create a backup of the source and load this onto the replica to cut down on the amount of time required for the replica to synchronize itself with the source. If the replica is also running NDB Cluster, this can be accomplished using the backup and restore procedure described inSection 21.7.9, “NDB Cluster Backups With NDB Cluster Replication”. 

ndb-connectstring=management_host[:port]

In the event that you are not using NDB Cluster on the replica, you can create a backup with this command on the source: 

shellS> mysqldump --master-data=1

Then import the resulting data dump onto the replica by copying the dump file over to it. After this, you can use themysql client to import the data from the dumpfile into the replica database as shown here, where_dumpfile_ is the name of the file that was generated using mysqldump on the source, and dbname is the name of the database to be replicated: 

shellR> mysql -u root -p db_name < dump_file

For a complete list of options to use withmysqldump, see Section 4.5.4, “mysqldump — A Database Backup Program”.
Note
If you copy the data to the replica in this fashion, you should make sure that the replica is started with the--skip-slave-start option on the command line, or else includeskip-slave-start in the replica'smy.cnf file to keep it from trying to connect to the source to begin replicating before all the data has been loaded. Once the data loading has completed, follow the additional steps outlined in the next two sections. 5. Ensure that each MySQL server acting as a replication source is assigned a unique server ID, and has binary logging enabled, using the row-based format. (SeeSection 16.2.1, “Replication Formats”.) In addition, we recommend enabling theslave_allow_batching system variable; beginning with NDB 7.6.23, a warning is issued if this variable is set to OFF. You should also consider increasing the values used with the--ndb-batch-size and--ndb-blob-write-batch-bytes options as well. All of these options can be set either in the source server's my.cnf file, or on the command line when starting the sourcemysqld process. SeeSection 21.7.6, “Starting NDB Cluster Replication (Single Replication Channel)”, for more information.