I am using an existing mysql role that works for a while in an existing farm - in a NEW farm.
Naturally it starts clean since there is no s3 snapshot available. However, the role is configured to use /mnt/mysql as its data dir. Since the /mnt dir is not part of the "synchronize all" process....it is not created nor restored from a snapshot (fresh db as I mentioned). The server therfore does not complete initialization and after a while terminates and a new instance is created - since it did not receive the "UP" event on time....known scenario. Is there any option to get over this in this state and not start with a totally new mysql role? For example....creating quickly the /mnt/mysql....starting the database and creating a snapshot before it auto terminates? Will this work? or maybe there is a better way.... currently I am in a loop. Thanks, Arie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
