[MDEV-10227] MariaDB Galera cluster gtid's falling out of sync inspite of setting wsrep_gtid_mode=ON Created: 2016-06-14  Updated: 2022-09-28  Resolved: 2017-12-25

Status: Closed
Project: MariaDB Server
Component/s: Galera, Replication
Affects Version/s: 10.1.11, 10.1.13, 10.1.14
Fix Version/s: 10.1.31

Type: Bug Priority: Major
Reporter: Kasturi Kalagara Assignee: Sachin Setiya (Inactive)
Resolution: Fixed Votes: 3
Labels: galera
Environment:

2.6.32-504.8.1.el6.x86_64

Issue Links:
Problem/Incident
is caused by MDEV-13431 wsrep_gtid_mode uses wrong GTID for t... Closed
is caused by MDEV-20720 Galera: Replicate MariaDB GTID to oth... Closed
Relates
relates to MDEV-29661 WSREP GTID Sync Inconsistency Version... Open

 Description   

I have asynchronous replication between 2 clusters (calling master cluster, slave cluster). As expected a node in the slave cluster receives async replication and galera transmits to the rest of the nodes of the slave cluster. When the gtid counter is being incremented on the nodes of this slave cluster, the node acting as the slave node is keeping track of master server id and incrementing the gtid by wsrep_domain_id, server_id, galera counter+1. However the other nodes of the slave cluster are not keeping track of the server id variable and increment gtid by wsrep_domain_id, galera counter+1. See below

Slave node of the slave cluster 

show variables like '%gtid%'; 
+------------------------+-------------------------+
 
Variable_nameValue
 
+------------------------+-------------------------+
 
gtid_binlog_pos2-100-36261
 
gtid_binlog_state2-200-36263,2-100-36261
 
gtid_current_pos1-100-36261
 
gtid_domain_id22
 
gtid_ignore_duplicatesOFF
 
gtid_seq_no0
 
gtid_slave_pos1-100-36261
 
gtid_strict_modeOFF
 
last_gtid2-200-36263
 
wsrep_gtid_domain_id2
 
wsrep_gtid_modeON
 
+------------------------+-------------------------+ 
11 rows in set (0.00 sec)

Another node in the slave cluster 

show variables like '%gtid%'; 
+------------------------+-------------------------+
 
Variable_nameValue
 
+------------------------+-------------------------+
 
gtid_binlog_pos2-100-36265
 
gtid_binlog_state2-200-36264,2-100-36265
 
gtid_current_pos1-100-36259
 
gtid_domain_id22
 
gtid_ignore_duplicatesOFF
 
gtid_seq_no0
 
gtid_slave_pos1-100-36259
 
gtid_strict_modeOFF
 
last_gtid
 
wsrep_gtid_domain_id2
 
wsrep_gtid_modeON
 
+------------------------+-------------------------+ 
11 rows in set (0.00 sec)

Please review and let me know if this is expected behavior or bug.

 Comments   
Comment by Geoff Montee (Inactive) [ 2017-08-02 ]

I added more details about this problem to MDEV-13431.

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

Patch for 10715 , will fix this

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