[Pacemaker] DRBD-MYSQL Pacemaker-Corosync won't failover

[Van Tonder, Raymond]

On 10/28/2011 9:28 AM, Andreas Kurz wrote:

> Hello,

> 

> On 10/28/2011 04:06 PM, Joe wrote:

>> Hello everyone,

>> 

>> My goal is to build a HA DRBD and MYSQL on two nodes(active/passive).
I

>> followed the " cluster from scratch" article to build this
environment.

>> If I do standby failover host, it works fine but when I pull the

>> heartbeat cable from the active node, the resources do not fail over
to

>> the secondary. Please advise. Thank you very much. Joe

> * "the" heartbeat cable == one heartbeat cable? Not supported setup --

> use at least two heartbeat channels, add at least the DRBD replication

> network.

> 

> * you produced a split brain situation. I'd expect you see errors in

> your cluster status and see DRBD log entries with a wording similar to

> "not allowed to become primary because allow-two-primaries is not set"

> ... if you had also pulled DRBD link you would have all resources

> running twice

> 

> * use stonith to recover from a split-brain situation (or block if its

> unsuccessful)

> 

> * read more manuals ;-)

> 

>> *CENTOS 5.6/drbd8.3/corosync/pacemaker

>> 

>> node-0 IP: 192.168.1.101 (heartbeat) 10.0.0.10 (drdb)

>> node-1 IP: 192.168.1.102 (heartbeat) 10.0.0.20 ( drbd)

>> Cluster Virtual IP: 192.168.1.160

>> 

>> * _crm configure show_

>> node $id="2b68511d-b96f-4b56-9f66-70262e3e2c46" mysqldrbd01 \

>>      attributes standby="off"

>> node $id="d86dc58b-2309-43d9-af96-6519127e83d7" mysqldrbd02 \

>>      attributes standby="off"

> These ids are from Heartbeat CCM ... but you attached a Corosync

> configuration? Decide for one ... either Heartbeat or Corosync.

> 

> Regards,

> Andreas

> 

> 

> 

 

I would suggest adding a third node (without the mysql and drdb) just
for quorum/heartbeat checking 

 

 

 


To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: 
https://www.fnb.co.za/disclaimer.html 

If you are unable to access the Disclaimer, send a blank e-mail to
firstrandbankdisclaimer at fnb.co.za and we will send you a copy of the Disclaimer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111028/f9c981dc/attachment-0003.html>