I want to ensure that mysql data persists when a farm shutsdown or fails. I thought that this would be possible by configuring the master mysql server to use an EBS volume as the location for the mysql data so I set the role to mount and EBS volume automatically and then changed the mysql config on the master to set the data directory to the mounted EBS volume.
When first setup this worked - the EBS volume mounted without requiring a resynch and then I copied the current mysql data to (with mysql down) and restarted the server. The problem is, having synchronised this change and terminated then launched the farm the mysql master seems to be starting mysql and mounting a temporary volume (per normal process) during start up. Once the EBS volume mounts it obscures the temporary volume created at start up with the EBS volume. The result is that all the databases and configuration, etc are missing - mysql root user has a null password and there are no databases despite the database folder and files being precent in the EBS mount. Restarting the mysql server resolves part of this - the data becomes available and users appear, with correct passwords. But the special users that are setup by scalr no longer work (I think they must get new passwords each time the system boots) Is there anyway to get the mysql master to delay setting up mysql until after the EBS volume has mounted and then not fetch any data bundle or otherwise attempt to initialise the system? Thanks Damon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
