1) stop the slave threads on B and C
2) stop writes to A using FLUSH TABLES WITH READ LOCK.
2.1) set read_only=true on A to prevent any writes if the read lock is
2.2) get A's coordinates with SHOW MASTER STATUS
3) issue START SLAVE UNTIL ... on B using the coordinates from A's SHOW
4) issue SHOW MASTER STATUS ON B
5) START SLAVE UNTIL ... on C using the coordinates from B
6) Issue SHOW MASTER STATUS on C
7) Issue CHANGE MASTER TO on A with coordinates from C
8) Issue CHANGE MASTER TO on C with coordinates from A (captured in step
10) Release READ LOCK (with UNLOCK TABLES) on A
11) A should remain read_only to prevent unexpected writes to it
12) send writes to C
On Thu, Oct 25, 2012 at 11:47 AM, Sabika M <sabika.makhd...@gmail.com>wrote:
> I have replication setup in the following way:
> A -> B ->C
> I am making updates to server A. I want to stop all my updates and point
> I guess what I am really asking is if the data is the same, is a backup
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.