MySQL Forums
Forum List  »  Replication

Re: Got fatal error 1236 from master when reading data from binary log
Posted by: Rick James
Date: January 21, 2013 10:41AM

> Client requested master to start replication from impossible position

_Usually_ this means that the Master crashed and that sync_binlog was OFF. The solution is to CHANGE MASTER to POS=0 of the next binlog file (see the Master) on the Slave.

The cause: The Master sends replication items to the Slave before flushing to its binlog (when sync_binlog=OFF). If the Master crashes before the flush, the Slave has already logically moved past the end of file on the binlog. When the Master starts up again, it starts a new binlog, so CHANGEing to the beginning of that binlog is the best available solution.

A longer term solution is sync_binlog=ON, if you can afford the extra I/O that it causes.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Got fatal error 1236 from master when reading data from binary log
25794
January 21, 2013 10:41AM


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.