Hello,

I would also like to hear ideas on this, but my thoughts are two:

1) This is why it is recommended that the heartbeat connection takes place
through a different network, even, if possible, a cross-over cable, or a
serial cable.  This way, even if the switch dies, the two nodes would still
communicate.

2) This is why a STONITH  mechanism is suggested, I understand.

Maybe someone can shed a different light on this issue :)

Jonás.

On Jan 14, 2008 7:47 PM, Michael Brennen <[EMAIL PROTECTED]> wrote:

> On Monday 14 January 2008 12:33, Lino Moragon wrote:
> > Hi list,
> >
> > I've got 2 questions concerning the prevention of splitbrain and
> > monitoring MySQL Server 5.
> > I'm testing a MySQL Server 5 with 3 instances on a CentOS 5.1 with
> > Heartbeat and DRBD on a 2 Node Cluster (active / passive)
> > At the moment my 2 Nodes are running on a VMware Server.
> >
> > I use the following Versions:
> > heartbeat v. 2.0.8-1
> > DRBD v. 8.0.6
> > For heartbeat style I'm using Release 1.
> >
> > I've configured on each 2 NICs, 1 for DRBD sync and heartbeat and
> > another one for heartbeat.
> >
> > haresoures:
> > mysql1  drbddisk::r0 Filesystem::/dev/drbd0::/pool/mysql/::ext3
> > 172.16.100.110 mysqld_multi
> >
> > My Questions:
> > 1. If I unplug both NICs of the active Node,  I get a Splitbrain after I
> > reconnect them again.
> > Is there any solution to prevent this using heartbeat R1 or which
> > possibilities would I have with R2?
>
> That sounds normal, as both machines then think they can become primary.
>
> Do you have a fence mechanism in place so the secondary can forcibly take
> the
> former primary out of service?
>
> > 2. How can I tell heartbeat to make an automatic failover to my passive
> > node if any of my MySQL Process has a hangup or terminates?
> > Can you monitor these processes and in cause of failure provoke an
> > automatic failover? If yes, which tools would I have to use?
>
> That I'm not sure, I will be awaiting the answer myself. :)
>
> --
>
>   -- Michael
>
> _______________________________________________
> 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

Reply via email to