On Feb 20, 2008 8:53 PM, Damon Estep <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:linux-ha- > > [EMAIL PROTECTED] On Behalf Of Damon Estep > > Sent: Wednesday, February 20, 2008 12:49 PM > > To: General Linux-HA mailing list > > > Subject: RE: [Linux-HA] how to mysql circular replication move IP > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:linux-ha- > > > [EMAIL PROTECTED] On Behalf Of Andreas Kurz > > > Sent: Wednesday, February 20, 2008 12:43 PM > > > To: General Linux-HA mailing list > > > Subject: Re: [Linux-HA] how to mysql circular replication move IP > > > > > > On Feb 20, 2008 8:09 PM, Damon Estep <[EMAIL PROTECTED]> wrote: > > > > I am trying to; > > > > > > > > > > > > > > > > Run mysql on a two node cluster (active/active) with circular > > > > replication enabled <- I have already set this setup > > > > > > > > > > > > > > > > Run two virtual IPs, one on each node when both nodes are healthy > > and > > > > mysql is running <- also apready running > > > > > > > > > > > > > > > > Move the IP from the failed node to the good node if the node > fails > > > > (easy enough) or if mysql fails <- my challenge > > > > > > > > > > > > > > > > How can I create a constraint that says; > > > > > > > > > > > > > > > > Run this ip resource on this node if mysql is running, but move it > > to > > > > the other node if it is not? So that the IP prefers one node only > > if > > > my > > > > sql is running ,but will gotohe other node if it is not. > > > > > > I did a similar setup some times ago but I solved it by using two > > > mysql lsb scripts ... one for each instance: > > > > > > * on node1 "mysql_01" was responsible for starting the first mysql > > > instance and "mysql_02" was only a dummy > > > * on node2 "mysql_02" was responsible for starting the second mysql > > > instance and "mysql_01" was only a dummy > > > > > > So only two simple groups and two location constrainst were needed. > > > > > > Regards, > > > Andreas > > > > > > > [Damon Estep] Makes sense, there is no reason a start cannot be sent > to > > the mysql service as it appears it will not start a second instance as > > a > > result. > > > > Thanks for the tip. > > > > Damon > > [Damon Estep] > > Sounded good, there is a problem though, when the dummy mysql_02 > migrates back to its preferred node it stops the service on node1.
Hmmm ... No, why do you think so? It's an independent init script that does not affect the other mysql instance. > > I assume you were dealing with a V1 or crm=no cluster? No, crm=yes > > Did you do something special to make the instance really a dummy, like > two different init scripts? In fact it was a LSB compliant init script for rinetd, configured to redirect the request for the second mysql instance to the first one ... and the other way round on the other node. So it was not exactly the same setup as yours because I had to start the IP resources prior to mysql because mysql only listened to a specific IP. Nevertheless it should also work for your setup. Regards, Andreas > > > Damon > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
