MySQL Forums
Forum List  »  Replication

Advanced Search
New Topic

Replication fails when mysql has been idle for a long time
Posted by: Christer Palm
Date: December 23, 2013 03:45AM

Hi!
I'm having some trouble with replication and mysql 5.1.69.

It appears that replication fails if the master goes down after having been idle for a long time (more than expire_logs_days number of days is the key, I suppose).

What seems to be happening is that the binary log file that was active at the time the master went down is immediately removed when the master comes back up again, resulting in a "fatal error 1236 from master" "Could not find first log file name in binary log index file" on the slave side when it reconnects to the master.

Is there anything I can do to prevent this behaviour? While the problem appears to be quite obvious, I haven't been able to find any information about it.

Regards,
Christer Palm

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Views
Written By
Posted
Replication fails when mysql has been idle for a long time
1529
Christer Palm
December 23, 2013 03:45AM
Re: Replication fails when mysql has been idle for a long time
817
Rick James
December 25, 2013 04:18PM
Re: Replication fails when mysql has been idle for a long time
1215
Christer Palm
December 27, 2013 05:18AM
Re: Replication fails when mysql has been idle for a long time
721
Rick James
December 28, 2013 12:31PM


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.