[Pacemaker] Failover IP + One service on multi-node cluster only works on two nodes.

Bright Dadson losintikfos at yahoo.co.uk
Mon Oct 7 12:25:24 UTC 2013


Hi All,


Stack: pacemaker/heartbeat

My setup consists of multiple nodes, atleast three with below configs.

##Heatbeat config

autojoin none
bcast eth0
warntime 3
deadtime 6
initdead 60
keepalive 1
node lab-node01
node lab-node02
node lab-node03
crm respawn

#Cluster Resource Config

node $id="36796d7a-0e51-4881-a818-32baf7190bff" lab-node3
node $id="8e7d151b-6ae5-48f0-b852-a5f753272986" lab-node1
node $id="c51c6359-bc6a-4920-aadf-b5676f40036b" lab-node2
primitive failover-ip ocf:heartbeat:IPaddr \
    params ip="10.5.5.34" \
    op monitor interval="10s"
primitive failover-mysql lsb:mysql.server \
    op monitor interval="15s"
group farm failover-ip failover-mysql
property $id="cib-bootstrap-options" \
    dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \
    cluster-infrastructure="Heartbeat" \
    stonith-enabled="false"


IP failover between lab-node01 and lab-node02 works fine interchangeably. The problem here is, when both lab-node01 and lab-node02 goes offline - lab-node03 do not take VIP and therefore the IP failover do not work.

Can I get lab-node3 to take over.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131007/84a93db5/attachment-0003.html>


More information about the Pacemaker mailing list