I repeated the process again..."synchronize all" on the sql master.
after bundling two new instances were born....when the first one became "running" it was marked slave and the original master was taken down. This resulted in 2 running slaves and a 3rd instance (the second of the newly born instances) initializing.... Even if this 3rd server will become a master eventually....this process leaves me with no running master for my farm for a substantial time which means no writes are enabled. Something seems wrong here. On Dec 25, 4:40 pm, afishler <[email protected]> wrote: > seems like there is no dns entry for the master so they are actually > both slaves. How do I get out of this situation? > > On Dec 25, 4:22 pm, afishler <[email protected]> wrote: > > > I "synchronized all" on the master mysql. > > > After it completed, currently the control panel displays that both are > > slaves. > > > The log indicates that one has "I'm first: 1" and the other 0. Does > > this mean that one is actually the master? (the one having first=1), > > is this just a display error or there is more to that. > > > Also - the two instances have the same up time....is the way scalr > > handles mysql synchronizing is by bringing up 2 new instances, loading > > the database backup and then taking the 2 existing instances together? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
