Hi, 1. Each farm could have only one MySQL role enabled at the moment. First instance started in this role is master and all the others are slaves. 2. Scalr has no ability of monitoring instance services. So slave to master promotion only happens when the master instance is being terminated. 3. Once you have chosen 'EBS' as MySQL data storage engine, you should not manage EBS volumes for this instance by hands, using EBS tab. All the needed operations are performed by Scalr.
Regards, Nick On Sun, Mar 29, 2009 at 4:53 PM, QXSystems <[email protected]> wrote: > > Hi, > > We have a open SCALR setup and we created a FARM and we have certain > queries as mentioned below. Please help us. > > 1. While creating new additional instance in MySQL role is getting > started as Master rather than Slave? > 2. When we stopped the MySQL services in Master the slave is not > changed as master? why? > 3. While we setup the EBS details in FARM edit page for the mysql role > as Create volume as --GB (even for attach snapshot option) and Auto > mount this volume into --- options selected but we check for it the > volume is created and its not assigned to the respective instance and > its also not mounted. why? > > > Thanks > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
