Jumped the gun I guess - It was almost ten minutes after termination of the master that I rebooted the slave. I thought failover would be a bit quicker.
Since I'm a write-heavy application, I'm only using the slave for failover and for fast EBS snapshots that don't impact the master. But it seems like for failover, the master would re-appear and be ready to go again faster than a slave will be promoted. I wonder if there's any advantage to having the slave for failover? On Jan 21, 2:12 pm, Alex Kovalyov <[email protected]> wrote: > You rebooted it when slave was in proccess of becoming master, so it > never ended up with that. > > you may try executing /usr/local/aws/slave2master.sh or terminating it > again. > > On 21 янв, 22:07, Rod Frey <[email protected]> wrote: > > > Just rebooted the "slave". Reboot from the scalr menu wouldn't take > > so I rebooted from a ssh session. It came back up and was still a > > slave. > > > In a bit of a panic here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
