MySQL Forums
Forum List  »  Replication

Restoring a broken slave
Posted by: Dan Casey
Date: August 29, 2005 09:27AM

mysql 4.0.20
myIsam tables..

I have two slave setups. One slave is fine and up to date. The second one which also updates off the same master showed the following.

Slave_IO_Running: Yes
Slave_SQL_Running: No

I have had this issue before. In which case I run slave stop; slave start; and then it starts working again. This time around, Slave_SQL_Running remained as "NO"..
There was a duplicate entry (which im not sure how that happened here if it didn't on the other slave). Im guessing thats where it stopped?

Right now im reloading lastnights master snapshot.. just to give this slave a more current db.

My questions are these.

1. I know im going to have to make a new mysqldump of the master, and record its current position in order to get replication started again. Is there a way that I can do this without disrupting service on my web site.. Or am I going to have to expect some downtime while the master is out?

2. How did this happen, or better yet, what can or should i do in the future?

3. almost forget, but since i am completely making a new slave here, is it safe to rm -rf all the bin-log and relay-bin-logs on this slave


Options: ReplyQuote

Written By
Restoring a broken slave
August 29, 2005 09:27AM
September 12, 2005 03:08PM

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.