MySQL GTID metadata not synced upon full SST
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.6 |
Fix Committed
|
Undecided
|
Unassigned | |||
5.7 |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Tested with Server version: 5.6.35-81.0-56-log Percona XtraDB Cluster (GPL), Release rel81.0, Revision 7f9b6ae, WSREP version 26.20, wsrep_26.20
When new node is added to a cluster, where all nodes are GTID enabled, after successful full SST, the joiner has unset initial GTID position.
Test case:
* bootstrap first node with settings:
server-id=1
enforce_
gtid_mode=on
log_slave_updates
log-bin=
* execute some writes
* start second node with same settings
* example result:
percona1 mysql> show global variables like 'gtid%';
+------
| Variable_name | Value |
+------
| gtid_deployment
| gtid_executed | 102cd5f1-
| gtid_mode | ON |
| gtid_owned | |
| gtid_purged | |
+------
5 rows in set (0.00 sec)
percona2 mysql> show global variables like 'gtid%';
+------
| Variable_name | Value |
+------
| gtid_deployment
| gtid_executed | |
| gtid_mode | ON |
| gtid_owned | |
| gtid_purged | |
+------
5 rows in set (0.03 sec)
* execute more writes, and see out of sync positions:
percona1 mysql> show global variables like 'gtid_e%';
+------
| Variable_name | Value |
+------
| gtid_executed | 102cd5f1-
+------
1 row in set (0.00 sec)
percona2 mysql> show global variables like 'gtid_e%';
+------
| Variable_name | Value |
+------
| gtid_executed | 102cd5f1-
+------
1 row in set (0.00 sec)
Quick test on PXC 5.7.16 worked well though, GTID was synced properly.
Hmmm.. everything works ok for me with 5.6.35-26.20 and 5.6.35-26.20.v3 (this is the one that is being used above).
Do you have the logs for the second node?