Known Issues in NDB Cluster Replication ignore-db  to filter databases or tables being replicated, you must take care not to block replication or binary logging of the  mysql.ndb_apply_status , which is required for replication between NDB Clusters to operate properly. In particular, you must keep in mind the following: Using  --binlog-do-db= db_name  (and no other  --binlog-do-db  options) means that changes  only  to tables in database  db_name  are written to the binary log. In this case, you should also use  --replicate-do-db=mysql ,  --binlog-do-db=mysql , or  --replicate-do- table=mysql.ndb_apply_status  to ensure that  mysql.ndb_apply_status  is populated on replicas. Using  --binlog-ignore-db=mysql  means that no changes to tables in the  mysql database are written to the binary log. In this case, you should also use  --replicate-do- table=mysql.ndb_apply_status  to ensure that  mysql.ndb_apply_status  is replicated. You should also remember that each replication rule requires the following: If you are replicating an NDB Cluster to a replica that uses a storage engine other than  NDB , the considerations just given previously may not apply, as discussed elsewhere in this section. NDB Cluster Replication and IPv6.   Beginning with NDB 8.0.22, all types of NDB Cluster nodes support IPv6; this includes management nodes, data nodes, and API or SQL nodes. Prior to NDB 8.0.22, the NDB API and MGM API (and thus data nodes and management nodes) do not support IPv6, although MySQL Servers—including those acting as SQL nodes in an NDB Cluster —can use IPv6 to contact other MySQL Servers. In versions of NDB Cluster prior to 8.0.22, you can replicate between clusters using IPv6 to connect the SQL nodes acting as source and replica as shown by the dotted arrow in the following diagram: 4617 2. Its own  --binlog-do-db  or  --binlog-ignore-db  option, and that multiple rules cannot be expressed in a single binary log filtering option. For information about these rules, see Section 5.4.4, “The Binary Log” . 1. Its own  --replicate-do-*  or  --replicate-ignore-*  option, and that multiple rules cannot be expressed in a single replication filtering option. For information about these rules, see Section 17.1.6, “Replication and Binary Logging Options and Variables” . 2. Using  --replicate-ignore-db=mysql  means that no tables in the  mysql  database are replicated. In this case, you should also use  --replicate-do-table=mysql.ndb_apply_status  to ensure that  mysql.ndb_apply_status  is replicated. 1. Using  --replicate-do-db= db_name  (and no other  --replicate-do-*  or  --replicate- ignore-*  options) means that  only  tables in database  db_name  are replicated. In this case, you should also use  --replicate-do-db=mysql ,  --binlog-do-db=mysql , or  --replicate-do- table=mysql.ndb_apply_status  to ensure that  mysql.ndb_apply_status  is populated on replicas.