content_image/856191.jpg
<img src='content_image/856191.jpg'>

Binary logging can be set to different formats for different tables by inserting rows into the ndb_replication  table using the appropriate db , table_name , and binlog_type  column values. The internal integer value shown in the preceding table should be used when setting the binary logging format. The following two statements set binary logging to logging of full rows ( NBT_FULL , internal value 3) for table test.a , and to logging of updates only ( NBT_UPDATED_ONLY , internal value 2) for table test.b : 

# Table test.a: Log full rows INSERT INTO mysql.ndb_replication VALUES("test", "a", 0, 3, NULL); # Table test.b: log updates only INSERT INTO mysql.ndb_replication VALUES("test", "b", 0, 2, NULL); 

To disable logging for one or more tables, use 1 ( NBT_NO_LOGGING ) for binlog_type , as shown here: 

# Disable binary logging for table test.t1 INSERT INTO mysql.ndb_replication VALUES("test", "t1", 0, 1, NULL); # Disable binary logging for any table in ’test’ whose name begins with ’t’ INSERT INTO mysql.ndb_replication VALUES("test", "t%", 0, 1, NULL); 

## 23.6.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 (see Section 23.6.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: 

