GTID replications fails to resume after master disconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
New
|
Undecided
|
Unassigned | ||
5.6 |
New
|
Undecided
|
Unassigned |
Bug Description
The slave was unable to connect to the master due to network issues. Once the network issues were resolved the slave did not continue replication even though SHOW SLAVE STATUS listed "Waiting for master to send event"
We sometimes see similar issues when the master is restarted.
The issue appears to be specific to GTID replication.
Repeated executions of SHOW SLAVE STATUS\G contained the following excerpt.
Slave_
9f9bf362-
After executing "STOP SLAVE; START SLAVE;" the slave resumed replication and Seconds_
Slave_
9f9bf362-
mysql Ver 14.14 Distrib 5.6.25-73.1, for Linux (x86_64) using 6.0
Server version: 5.6.25-73.1-log Percona Server (GPL), Release 73.1, Revision 07b797f
CentOS release 6.5 (Final)