[Linux-cluster] MySQL Failover / Failback
Robert Gil
Robert.Gil at americanhm.com
Thu Jul 26 21:24:39 UTC 2007
Well, if you prevent mysql from starting on boot, your load balancer
should recognize that and not fail back to that server. We took mysql
itself out of the cluster since we also do replication. It was not
necessary to have it in there for our application.
Rob Gil
Linux Systems Administrator
American Home Mortgage
________________________________
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Bjorn Oglefjorn
Sent: Thursday, July 26, 2007 4:33 PM
To: linux clustering
Subject: Re: [Linux-cluster] MySQL Failover / Failback
Thanks Rob, but that's not quite what I'm looking for. I have a
middleware script of my own which allows me to have both nodes with
mysql running at all times. I need to ensure that when the MASTER
fails, Cluster Suite will failover to the SLAVE. My script then
performs some SQL ops to allow writes, etc. When the MASTER comes back
from being fenced, I need to make sure that Cluster Suite does not
failback to the MASTER. I'm hoping that the 'nofailback' option exists
and will work as I expect it to.
--BO
On 7/26/07, Robert Gil <Robert.Gil at americanhm.com> wrote:
I had figured this out a while back and forgot to post back to
the list.
The steps are as follows
Create a child script to the virtual ip to check whether mysql
is up.
Have mysql NOT start on boot.
With these two things done. When the vip fails over, it will not
fail
back because mysql wont be up.
Rob Gil
Linux Systems Administrator
American Home Mortgage
________________________________
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Bjorn
Oglefjorn
Sent: Thursday, July 26, 2007 3:18 PM
To: linux clustering
Subject: Re: [Linux-cluster] MySQL Failover / Failback
I found that a 'nofailback' option was added for the
<failoverdomains>
section of the conf. I can't find any reference to 'nofailback'
in any
RHCS doc I can find. I'm guessing it should look like this:
<failoverdomain name="test_failover_domain" ordered="1"
restricted="1" nofailback="1">
...
</failoverdomain>
Can someone confirm? I will attempt to confirm this myself and
will
report back when I know for sure.
--BO
On 7/26/07, Bjorn Oglefjorn <sys.mailing at gmail.com> wrote:
I'd love to know how to do this as well. Anyone?
--BO
On 6/1/07, Robert Gil <Robert.Gil at americanhm.com
<mailto:Robert.Gil at americanhm.com > > wrote:
1) Node 1 (master) dies
-How do we enable "sticky" failover so
that it
does not then fail back to Node 1
--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20070726/0861537d/attachment.htm>
More information about the Linux-cluster
mailing list