Online GTID gtid_deployment_step replication discrepancy
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
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
Online GTID deployment
https:/
Online GTID rollout now available in Percona Server 5.6
https:/
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?