Master binary log rotation not proper after restarting mysql server?
After restarting mysql master server,it rotates binlog file and update Previous-GTIDs at initial header. but in one of our server it has not updated this value so gotting ": Got fatal error 1236 from master when reading data from binary log: 'Error reading header of binary log while looking for the oldest binary log that contains any GTID that is not in the given gtid set'" at SLAVE.
Here is the contents of binary new binary log file,
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 4
#140314 18:43:41 server id 1 end_log_pos 120 CRC32 0x2b2ead2b Start: binlog v 4, server v 5.6.16-log created 140314 18:43:41
# Warning: this binlog is either in use or was not closed properly.
BINLOG '
3U0jUw8BAAAAdAAAAHgAAAABAAQANS42LjE2LWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAASut
Lis=
'/*!*/;
# at 120
#140315 16:35:12 server id 1 end_log_pos 168 CRC32 0x80784e26 GTID [commit=yes]
SET @@SESSION.GTID_NEXT= 'd5146594-ab7d-11e3-a120-90e2ba45437e:118'/*!*/;
# at 168
Could i know the reason in which condition this may occur. I m unbale to trace it.
Thanks
Subject
Views
Written By
Posted
Master binary log rotation not proper after restarting mysql server?
2233
March 17, 2014 08:58AM
957
March 17, 2014 01:41PM
940
March 18, 2014 06:31AM
1021
March 18, 2014 06:57AM
932
March 19, 2014 04:49PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.