Getting below error whenever an existing slave tries to align to new-master when old-master goes down. We usually do slave promotion to master, suppose we have master<–slave1/slave2 after performing DB promotion for slave2 to master, topology becomes slave2(new-master)<-- slave1. Slave1 replication breaks when it start try to replicate to its new-master. Please suggest if you have ever experienced same issue and solved it.
’
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: ‘The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.’
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 168954657
Master_UUID: d53c996f-17f4-11e8-bffd-06345d1b6210
Master_Info_File: /mnt/db/mysql/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp: 180424 15:47:09
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set: 0e197096-73bb-11e7-a12a-06ca36b1e1ed:1-99439426,
34aeff8f-f073-11e7-a56c-0214b016c4b8:1-183468,
418b5f15-47d6-11e8-a517-02633c772f1c:1-287,
5ad8c560-db75-11e7-9251-06309d9466a8:1-152007,
7c491fc7-d9e4-11e7-bdce-020546577760:1-11407,
7df2a614-db71-11e7-9b3d-020546577760:1-76705617,
b1d0436a-1239-11e8-af2a-022fcffdfaf0:1-384671,
c4a41e14-0b60-11e8-9f91-06345d1b6210:1-49588,
c7fe5ac2-8bfd-11e7-8ccb-02e178303485:1-2156
Auto_Position: 1
Replicate_Rewrite_DB:
Channel_Name: