On 15 Sep., 21:03, Frédéric Sidler <[email protected]> wrote: > 1. you can use a mysql slave for snapshot only. This instance will be used > for backup only and not for your reads. This is not the most cost effective > solution, but this avoid a delay after a snapshot.2. if you start a new > slave, restart mysql-proxy only when the new slave is in sync with the > master.
I'm not sure if I understood you right. Let me rephrase your suggestion: I should always have an instance of mysql-slave running but never use it. When scaling up the unused mysql-slave becomes a read-only backend and the newly launched instance will be idling (after loading the snapshot and catching up to the master) until everything scales up again. This way there is always a spare server which is always in sync and can be ready within seconds. I love that idea for having a slave ready without even waiting for the bootup! Cheers, Mario --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
