|
|||||||||||
|
Changing masters
From: Jez Quiggley <jez.quigley(at)gmail.com>
Date: Thu Sep 27 2007 - 04:57:41 EDT
I am about to change Slave 1, S1 to be the new master. Binary logging is enabled on all three servers and replication grants appear to be OK. The way I have done this in the past is: On M1 - flush logs Point our applications at S1 to do read/writes On S2 - stop slave ; change master to new_master ; reset slave ; start slave On M2 - change master to new_master ; reset slave ; start slave My concern is that if I for whatever reason am unable to get the old master, M1 and the secondary slave to replicate with my new master, S1. Normally I would just fix whatever issue I had then refresh the slave using a mysqldump with --master-data to get me back up and running but in this setup, not having a replication slave for any length of time would be a very bad thing. Have I any way of mitigating any risk other than making S2 a slave of S1 before making S1 a master? Any other thoughts on making this go smoothly? Dave Received on Thu Sep 27 04:58:02 2007 This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 10:14:24 EDT |
||||||||||
|
|||||||||||