On 2010-10-29 11:17, Alan Hodgson wrote:
I'm curious about this too. It seems that currently I'd have to rebuild any additional slaves basically from scratch to use the new master. I think so long as you "pointed" (via primary_conninfo) the additional slaves to the new (pending) master, before you "touch"ed the pending master's trigger file, you should be OK, as all the DBs should be in sync at that point. When the primary DB server goes down, updates are no longer accepted. In such a situation, the human goal is to get the updates accepted again, and human beings in a hurry are apt to forget the exact sequence of steps to follow. If one forgets, and enables the new master without "repointing" the other slaves, then you have a situation where you have to backup/restore the new primary to each of the slaves, in order to recover the slaves. The failover shouldn't be that brittle. A similar situation exists when having to reboot all the DB servers (say, for maintenance), or just reboot one in a period where you can afford to suspend updates: As near as I can tell (and I will find out over the weekend), the correct procedure is to stop the primary FIRST, and then reboot whatever slaves you need, and then reboot (if needed) or restart the primary. I wonder if this thread should be in the "ADMIN" group (and if so, should I repost the original message there) ??? -- Mail to my list address MUST be sent via the mailing list. All other mail to my list address will bounce. |
