MySQL Forums
Forum List  »  Replication

Re: Restarting Slave After Master Crash
Posted by: Rafael Rodriguez Jr.
Date: January 12, 2007 01:02PM

i guess this thread seems dead but i ran into the same problem and this is how i fixed it. It seems that the MYSQL just needs the reference/starting point in the log so it can resume replication.

Try this

STOP SLAVE

FLUSH TABLES WITH READ LOCK;

SHOW MASTER STATUS (record these valuse it will state name of file and position)

UNLOCKTABLES;

CHANGE MASTER TO MASTER_LOG_FILE='recorded_log_file_name',
CHANGE MASTER TO MASTER_LOG_POS=recorded_log_position;

START SLAVE


you may still get an error message at first in the logs but replication should resume

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Restarting Slave After Master Crash
9658
January 12, 2007 01:02PM
5915
October 19, 2008 03:21PM


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.