Hey folks, due to a variety of reasons, I am running a single, master mysqllvm64 instance (c1.xlarge) - in fact it's actually slaved to an external machine and until we can move all our stuff to the cloud, we won't add any more slaves to the actual farm. Farm id is 1395.
In the meantime, I am crossing my fingers and trying to figure out a way of saving the mysql data frequently. Apparently, as it's a single instance and no slaves are running, scalr won't do backup. Only bundling is possible right now. I had set the bundling frequency to 2 hours (the snapshot takes about 30 minutes to upload) and it seemed to be working fine when out of the blue Saturday night, I noticed the mysql server had essentially gone away. The mysqld process had died but I couldn't even kill it no matter how many "kill -9"s I did. In my experience, this kind of stuff usually happens when the file system is hosed - I suspect /mnt/mysql- data to be gone. I issued a reboot command - however, scalr terminated the instance and started a new one. After a couple of hours of work, I was able to get the new instance up and running from the last available bundle. However, I noticed another possible bug - the static IP assigned by scalr to the previous master was not being attached to the new one. Yet, scalr definitely knew I had enabled the elastic ip option for the role. In the end, I had to attach the static IP manually. Right now, my farm, still running at one instance, has a bundling interval of 24 hours. I wonder if very frequent bundling can lead to file system corruption. Anyone else experienced anything similar? Finger crossed ... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
