-
Frazer Clement authored
Implement propagation of applied epochs via ndb_apply_status table. A new MySQLD option --ndb-log-apply-status is added which causes a MySQLD acting as a Slave to log mysql.ndb_apply_status updates received from its immediate Master in its Binlog with its own Server Id. This allows them to propagate into the mysql.ndb_apply_status table(s) of downstream slaves. In a circular configuration they propagate back to the originating Cluster. In chained-slave replication scenarios, this gives downstream slaves visibility of their position relative to all their upstream contributors. In circular replication scenarios, this gives a Master visibility of when its changes (epochs) have been applied to other Clusters in a replication circle. New testcase rpl_ndb_break_3_chain added. New testcase ndb_binlog_log_apply_status added. Testcase rpl_ndb_circular extended. This functionality is a basis for WL5353.
Frazer Clement authoredImplement propagation of applied epochs via ndb_apply_status table. A new MySQLD option --ndb-log-apply-status is added which causes a MySQLD acting as a Slave to log mysql.ndb_apply_status updates received from its immediate Master in its Binlog with its own Server Id. This allows them to propagate into the mysql.ndb_apply_status table(s) of downstream slaves. In a circular configuration they propagate back to the originating Cluster. In chained-slave replication scenarios, this gives downstream slaves visibility of their position relative to all their upstream contributors. In circular replication scenarios, this gives a Master visibility of when its changes (epochs) have been applied to other Clusters in a replication circle. New testcase rpl_ndb_break_3_chain added. New testcase ndb_binlog_log_apply_status added. Testcase rpl_ndb_circular extended. This functionality is a basis for WL5353.
Loading