Sam, This issue was finally resolved. Please confirm everything is ok now.
Nick 2009/8/12 Nickolas Toursky <[email protected]>: > Sam, > > Going to test this ourselves. > If you wish to help us with screenshots, please send them to either > [email protected] or [email protected]. > > Thank you, > Nick > > 2009/8/12 Sam <[email protected]>: >> >> Hi Nickolas, >> >> Thanks for your suggestion. >> I tried the same thing what you suggested. >> But yesterday I was getting the IP address of ext-4music-master-1- >> master.4music.c4tech.co.uk >> differently everytime, sometimes of master and sometimes slave. >> >> The main problem now is that if I wish to synchronize the role master >> with all the instances which includes slaves and master roles, >> the new instances come up as master i.e. it terminates master and >> slave servers and launches two master instances. >> I can see in the DNS the on-existence of slave after synchronization. >> >> I can send you screenshots of before synchronization and after >> synchronization if you wish to see what is actually happening. >> >> At the moment I have got 1 master and 1 slave. This is the correct one >> as after synchronization I terminated the farm and it comes up as >> right order. >> The problem is only when you SYNCHRONIZE database server which has got >> one or more slaves. >> >> Thanks >> >> On Aug 12, 9:54 am, Nickolas Toursky <[email protected]> wrote: >>> Hi Sam, >>> >>> Your role is called '4music-master-1', with the prefix ext- it is >>> resolved to ALL instances of this role - both masters and slaves >>> (79.125.42.85 and 79.125.59.56 ATM). >>> >>> If you wish to resolve master server, add a suffix '-master' to this domain. >>> For slave, add a suffix '-slave'. >>> >>> $ dig +short ext-4music-master-1.4music.c4tech.co.uk >>> 79.125.42.85 >>> 79.125.59.56 >>> >>> $ dig +short ext-4music-master-1-master.4music.c4tech.co.uk >>> 79.125.42.85 >>> >>> $ dig +short ext-4music-master-1-slave.4music.c4tech.co.uk >>> 79.125.59.56 >>> >>> Nick >>> >>> 2009/8/11 Sam <[email protected]>: >>> >>> >>> >>> >>> >>> > I can confirm that this is a consistent problem. >>> >>> > Once you start the farm and if you have master and slave role and then >>> > if you synchronize the MySQL master server then all the new instances >>> > of the master MySQL server >>> > are displayed as Master. In reality there should be just one master. >>> >>> > Please help as this will prevent us unable to deploy the project on >>> > Ec2. >>> >>> > On Aug 10, 2:48 pm, Sam <[email protected]> wrote: >>> >> Also, when I synchronized master, the slave was terminated and I have >>> >> two masters role now, which is a bit weird. >>> >> The farm ID is same 2213. >>> >>> >> On Aug 10, 12:49 pm, Sam <[email protected]> wrote: >>> >>> >> > Hi, >>> >>> >> > I have one load balancer, one MySQL master server and one MySQL slave >>> >> > server. >>> >> > When I am trying to ping the master MySQL (External DNS name) I am >>> >> > sometimes getting the IP address of master MySQL server and sometimes >>> >> > getting the slave IP address after consistently trying to ping. >>> >>> >> > The farm ID is 2213 and DNS name is ext-4music- >>> >> > master-1.4music.c4tech.co.uk >>> >>> >> > When you ping the above server I am sometimes getting 79.125.44.127 >>> >> > which is right but sometimes getting the IP address of slave >>> >> > 79.125.47.240 which is not right. >>> >> > They come from the same custom role. >>> >>> >> > Could you please help? >>> >>> >> > 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 -~----------~----~----~----~------~----~------~--~---
