Has anyone tested dropping a master database?
I have dropped the master database that was replicating just to see how it
would affect the slave. The slave kept its data.
What would the proper proceedure be in this case?
I wouldnt be able to snapshot the slave and then port the snapshot back into
the master, the bin logs would be messed up then.
If I was replicating multiple databases on the master (bin logging multiple
databases) and I had a slave only replicating one of those databases, I
wouldnt be able to just remove all the bin logs and start the process over
again without losing the rest of the replicated databases.
A note: Nothing occurs in the error log or in SHOW MASTER STATUS on the
master when a database is dropped that it is supposed to be replicating.
Does it not realize that the database is not there?
If I was only replicating one database (bin logging one database), could I
just port in a copy from the slave, remove the bin logs and index(or modify
it in some way) from the master, do something with the master.info on the
slave and then let it go from there?
Has anyone ever been through this scenario? (Luckily I am only testing these
things and I am not on a live database!)
Luc Foisy
Technical Magic Corporation
1 Stafford Road, Suite 325, Nepean, Ontario, K2H 1B9
Phone: (613) 829-7117 Fax: (613) 596-5096
E-Mail: [EMAIL PROTECTED]
<<<<< Fulfilling the Promise of Technology >>>>>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
