mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 11:01:52 +01:00
2fe6186124
Problem:- Gtid are not transferred in Galera Cluster.
Solution:- We need to transfer gtid in the case on either when cluster is
slave/master in async replication. In normal Gtid replication gtid are generated on
recieving node itself and it is always on sync with other nodes. Because galera keeps
node in sync , So all nodes get same no of event groups. So the issue arises when
say galera is slave in async replication.
A
| (Async replication)
D <-> E <-> F {Galera replication}
So what should happen is that all node should apply the master gtid but this does
node happen, becuase node E, F does not recieve gtid from D in write set , So what E(or F)
does is that it applies wsrep_gtid_domain_id, D server-id , E gtid next seq no. This
generated gtid does not always work when say A has different domain id.
So In this commit, on galera node when we see that this event is recieved from master
we simply write Gtid_Log_Event in write_set and send it to other nodes.
|
||
|---|---|---|
| .. | ||
| GAL-501.result | ||
| galera_certification_ccc.result | ||
| galera_certification_double_failure.result | ||
| galera_evs_suspect_timeout.result | ||
| galera_garbd.result | ||
| galera_gtid_2_cluster.result | ||
| galera_innobackupex_backup.result | ||
| galera_ipv6_mysqldump.result | ||
| galera_ipv6_rsync.result | ||
| galera_ipv6_xtrabackup-v2.result | ||
| galera_ist_gcache_rollover.result | ||
| galera_parallel_apply_3nodes.result | ||
| galera_pc_bootstrap.result | ||
| galera_pc_weight.result | ||
| galera_safe_to_bootstrap.result | ||
| galera_slave_options_do.result | ||
| galera_slave_options_ignore.result | ||
| galera_var_dirty_reads2.result | ||