-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GTID seqno counter gets desynchronized after CC #185
Comments
After adding some instrumentation it is now clear that the global seqno counter may get desynchronized between the nodes on configuration change, which essentially means a loss of action. Master log (cleaned up, showing transactions with checksums as unique IDs):
Slave 1 (joiner):
Slave 2 (donor):
it can be seen that at least master and slave2 see different transactions under global seqnos 32786 and 32788. And transaction with a checksum of 13960164137662801834 is seen as 32789 on slaves and 32790 on master. |
An even better view is here:
node2 (joiner):
node3 (donor):
Notably, again donor and joiner aborted. As can be seen node1 replicated action 867 which only it received. Curiously it was not the first action to be delivered (or sent) in new configuration. node3 was the first to replicate action 866 which was delivered by all nodes. |
Running stopcont.sh test with induced action fragmentation (to catch #172) leads to
apparently only on slaves
The text was updated successfully, but these errors were encountered: