Hi, I was hoping someone here might know the best way to setup a mySQL replication environment where master->slave can be flipped to slave<-master. NOTE: I am NOT looking for a master<=3D>master bi-directional updating solution. This is a solution for HA, so when the master "dies" the slave becomes the master and when the old master returns, it becomes the slave to the new master.
The docs are a little unclear on the details and don't indicate everything. It does say it can be done by setting the log-bin in the my.cnf on the slave, and so the slave is ready to become a master when issued a SLAVE STOP; RESET MASTER and CHANGE MASTER TO on the other slave. I have also check archives and could not find any answers. So here are my questions: 1. Are two different my.cnf files used? One when a machine is used as a slave and there when it is a master? The server-id is the same regardless if the server is a master or a slave? 2. Or are each machine setup to be the master of the other? Meaning they have both master and slave info in the my.cnf. 3. A question in regards to the documentation instructions, is the STOP SLAVE only done on the slave (getting ready to become a master) and the RESET MASTER and CHANGE MASTER TO done on the old master? Any help is great appreciated. Thanks!! ~Vicky --------------------------------------------------------------------- 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
