LP #1491682: GTID replications fails to resume after master disconnect

**Reported in Launchpad by monty solomon last update 05-09-2015 06:52:00

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_IO_State: Waiting for master to send event
Connect_Retry: 15
Master_Log_File: bin.010862
Read_Master_Log_Pos: 2528103
Relay_Log_File: relay.001675
Relay_Log_Pos: 307
Relay_Master_Log_File: bin.010862
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Exec_Master_Log_Pos: 2528103
Relay_Log_Space: 657
Seconds_Behind_Master: 0
Master_Server_Id: 1156476169
Master_UUID: 9f9bf362-83e9-11e4-a45f-0acf4ba07bb2
Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
Master_Retry_Count: 86400
Retrieved_Gtid_Set: 9f9bf362-83e9-11e4-a45f-0acf4ba07bb2:1-1233067
Executed_Gtid_Set: 90fe53a8-1a31-11e5-b854-122ff10e879b:1-6,
9f9bf362-83e9-11e4-a45f-0acf4ba07bb2:1-1233067

After executing "STOP SLAVE; START SLAVE;" the slave resumed replication and Seconds_Behind_Master changed from 0 to 3510

Slave_IO_State: Waiting for master to send event
Connect_Retry: 15
Master_Log_File: bin.010864
Read_Master_Log_Pos: 11834054
Relay_Log_File: relay.001679
Relay_Log_Pos: 16023
Relay_Master_Log_File: bin.010863
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Exec_Master_Log_Pos: 15825
Relay_Log_Space: 24322598
Seconds_Behind_Master: 3510
Master_Server_Id: 1156476169
Master_UUID: 9f9bf362-83e9-11e4-a45f-0acf4ba07bb2
Slave_SQL_Running_State: System lock
Master_Retry_Count: 86400
Retrieved_Gtid_Set: 9f9bf362-83e9-11e4-a45f-0acf4ba07bb2:1-1239713
Executed_Gtid_Set: 90fe53a8-1a31-11e5-b854-122ff10e879b:1-6,
9f9bf362-83e9-11e4-a45f-0acf4ba07bb2:1-1233654