MySQL Cluster Tutorial - cdn.oreillystatic.com

Luckily, the solution is rather simple. Just configure another SQL Node to do binary
logging.
Setting up Replication between Clusters
Setting up Geographical Replication between two Cluster is as simple as setting it up
between two ‘normal’ MySQL servers.
We’ll need to start a second Cluster for this.
shell> ndb_mgmd --initial -f /opt/mysqlcluster/config_Slave.ini --configdir=/
opt/mysqlcluster/ndb_Slave
shell> ndbd -c localhost:1187
shell> mysqld_safe --defaults-file=/opt/mysqlcluster/my_Slave.cnf &
To access the Slave MySQL Cluster using the ndb_mgm and mysql tool, use the following:
shell> ndb_mgm -c localhost:1187
shell> mysql -S /tmp/mysql_Slave
On the Master Cluster you create a MySQL user which has the REPLICATION USER privilege.
You have to do this on every SQL Node which you are doing binary logging:
shell> mysql
mysql_A> GRANT REPLICATION SLAVE ON *.* TO repl@127.0.0.1;
shell> mysql -S /tmp/mysql_B
mysql_B> GRANT REPLICATION SLAVE ON *.* TO repl@127.0.0.1;
The reason you need to do it on both is because the grant tables in MySQL are local to each
node. They are MyISAM and are not part of Cluster.
Now we need to the binary log position from which we are going to start the replication.
We will use the SQL Node A to start with.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 76/81