[MDEV-6866] Ensure consistency of sequence number in Galera GTID Replication Created: 2014-10-13  Updated: 2017-12-25  Resolved: 2017-12-25

Status: Closed
Project: MariaDB Server
Component/s: Galera
Fix Version/s: 10.0.34-galera

Type: Task Priority: Major
Reporter: Nicolas BLANC Assignee: Unassigned
Resolution: Won't Fix Votes: 4
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-20720 Galera: Replicate MariaDB GTID to oth... Closed

 Description   

I created a first Galera node (with MariaDB 10.0.13 Galera). Then, i attached 2 another nodes. After a while, i created another cluster. But the gtid_domain_id was the same within the 2 clusters...
It has broken a slave which was slave on both cluster (multi-master technology on mariadb 10.0.13 standalone).

After a while, i found the problem being 2 cluster having the same GTID domain. So i changed online the gtid_domain_id on the first cluster. But as the instruction is not replicated, it was not played at the same time on the 3 nodes. After the change, the sequence number of the couple (domain_id-server_id) for the server_id of the first node was differents on the 3 nodes! All writes comes from the first master... But on each node the sequence number is not the same (domain_id-server_id is the same). Definitively, i think that sequence must depend on the server receiving the writes... And transmit by the Galera framework, to ensure consistency of the sequence number.



 Comments   
Comment by Sachin Setiya (Inactive) [ 2017-12-25 ]

Actually 10.0-galera do not have wsrep_gtid_mode , so gtid support is buggy in 10.0-galera , but 10.1.31 wont have this issue.(patch for MDEV-10715 should have fixed this)

Generated at Thu Feb 08 07:15:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.