Online GTID gtid_deployment_step replication discrepancy

Bug #1542284 reported by monty solomon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
New
Undecided
Unassigned
5.7
Invalid
Undecided
Unassigned

Bug Description

I used gtid_deployment_step to convert multiple clusters to use GTID. After completing the conversions I ran pt-table-checksum and discovered that there were replication inconsistencies on a bunch of the clusters. Some of the changes on the new master were not replicated to the slaves.

The replication discrepancies appeared on clusters that were very busy. It appears that there may be a window during the process where the new master is writing binlog entries without GTIDs.

When exactly during the master/slave swap should the value of gtid_deployment_step be changed on the slave that will become the new master?

Online GTID deployment
https://www.percona.com/doc/percona-server/5.6/flexibility/online_gtid_deployment.html

Online GTID rollout now available in Percona Server 5.6
https://www.percona.com/blog/2015/02/10/online-gtid-rollout-now-available-percona-server-5-6/

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Monty, we have just learned that gtid_deployment_step would release any FTWRL on that connection (bug 1549229). Do you use FTWRL here? Would that help to explain your symptoms?

tags: added: gtid-deployment-step
Revision history for this message
monty solomon (monty+launchpad) wrote :

That does bug not seem to be related.

Revision history for this message
monty solomon (monty+launchpad) wrote :

(Launchpad needs a feature to edit comments :-) )

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3374

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.