Announcement

Announcement Module
Collapse
No announcement yet.

mysql 5.6 GTID replication error

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • mysql 5.6 GTID replication error

    we recently upgraded from mysql 5.5 to 5.6.15 and enabled GTID based replication, now problem is for some reasons we restarted our slave and after that replication break.

    I Checked SHOW SLAVE STATUS error is "'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.''

    i am suspecting it happens because of master old binary log (7 days before) deleted form master as we are using expire_logs_days=7 and slave still looking for this old binary log for some GTID reference to replicate with master.
    I tried following link solution ,
    http://www.mysqlperformanceblog.com/...-in-mysql-5-6/
    but it still not working.
    Note :using mysql 5.6.15

    Now only option for me to re-create slave by taking mysqldump from master.

    Is there any other option if we can start replication without recreating new slave.


    Thanks in Advance

  • #2
    What do you mean by "restarted slave"? Was it not replicating for more then 7 days? Or was it restored with backup older then 7 days?

    If there are no longer binary logs on master containing the last executed position indeed, then how would you like to resume replication? In that case you can use Percona Xtrabackup to rebuild slave much faster (and without blocking master) then by using mysqldump.

    Comment


    • #3
      yes, it was replicating more then 7 days. I checked on master binary logs containing the last executed position was available, only 7 days before binary logs are deleted.
      Last edited by lalitvc; 01-20-2014, 12:55 AM. Reason: we restarted slave because of SWAP memory issue on server

      Comment


      • #4
        I'm not sure what exactly causing the problem,but i fixed replication by applying following fix.

        REPLICATION fix: 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.''

        slave_io_running stop running.

        eg. SLAVE UUID: 5c7sf77f-447e-11e3-b2c3-c80aa9g17dc9

        MASTER UUID: 4b37def1-6189-11e3-bfc0-e89a5f22a448


        SLAVE>show slave status;

        Note down last Executed_Gtid_Set position on slave

        eg. '5c7sf77f-447e-11e3-b2c3-c80aa9g17dc9:1-83345127, 4b37def1-6189-11e3-bfc0-e89a5f22a448:1-2:7:12:17:22:27:32:37-38:43:48:53:58:71:76-160:165:170:175:180:185:190:195:200-232:241:246:255:260:265:270-347:352:357:362:367:391-397:404-407:412:417:419:421-424:427-434:436-5550:5555-5558:5560-5568:5571-5603:5606-5619:5627-5634:5637-5642:5646-5647:5650-5654:5657-5660:5662-5692:5695-5698:5701-5707:5709-5710:5715-5719:5721-5758:5779-6916:6918-11347:11349-11358:11362-11661:11673-11902:11906-11920:11937:11942:11947-12706:12711:12720-12800:12805:12810:12815:12820:12825:12830-12973:12978:12980-12982:12986:12991:12996:13001:13006:13011:13016:13 021:13026-13030:13032-13317:13322-13325:13328-653183:653185-654126:654128-1400817:1400820-3423394:3423401-5779965'
        (Here 5779965 is MASTER last Executed_Gtid on slave )


        slave>stop slave;

        slave> FLUSH TABLES WITH READ LOCK;

        SLAVE>show master status;

        '5c7sf77f-447e-11e3-b2c3-c80aa9g17dc9:1-83345127, 4b37def1-6189-11e3-bfc0-e89a5f22a448:1-2:7:12:17:22:27:32:37-38:43:48:53:58:71:76-160:165:170:175:180:185:190:195:200-232:241:246:255:260:265:270-347:352:357:362:367:391-397:404-407:412:417:419:421-424:427-434:436-5550:5555-5558:5560-5568:5571-5603:5606-5619:5627-5634:5637-5642:5646-5647:5650-5654:5657-5660:5662-5692:5695-5698:5701-5707:5709-5710:5715-5719:5721-5758:5779-6916:6918-11347:11349-11358:11362-11661:11673-11902:11906-11920:11937:11942:11947-12706:12711:12720-12800:12805:12810:12815:12820:12825:12830-12973:12978:12980-12982:12986:12991:12996:13001:13006:13011:13016:13 021:13026-13030:13032-13317:13322-13325:13328-653183:653185-654126:654128-1400817:1400820-3423394:3423401-5779965'

        (HERE 83345127 Last GTID executed on slave)



        slave>reset master;


        slave>set global GTID_PURGED='5c7sf77f-447e-11e3-b2c3-c80aa9g17dc9:1-83345127, 4b37def1-6189-11e3-bfc0-e89a5f22a448:1-5779965';

        SLAVE>start slave;

        SLAVE>unlock tables;
        SLAVE>show slave status;

        NOTE: After this Re-start other chain-slaves ,masters if they stop replicating;
        Last edited by lalitvc; 02-22-2014, 04:46 AM.

        Comment

        Working...
        X