Home / server / Questions / 350086
Accepted
user53864
Asked: 2012-01-16 07:47:49 +0800 CST

Heartbeat Pacemaker 3 node/ip failover

  • 772

I have setup two node active/active ip failover with heartbeat and pacemaker following the link at zivtech on the two load balancers for the backend web servers. Two LBs has public ip each which is shared for failover and I checked if the ips are taken over by available lb if one lb fails and it's doing fine. Now I want to add one more load balancer for one more public ip failover(totally 3 ips) and I guess it's not possible with heartbeat. How do I do this? Any suggestions please?

Thanks!

EDIT:1

Tried directly adding 3rd node in ha.cf file with autojoin any but crm_mon didn't show the third node as if it's added neither Online nor Offline.

ha.cf:

ucast eth0 192.168.1.2
ucast eth0 192.168.1.3
ucast eth0 192.168.1.4
.....
node lb1
node lb2
node lb3
........
autojoin any

crm_mon -1:

============
Last updated: Mon Jan 16 22:29:20 2012
Stack: Heartbeat
Current DC: lb2 (47f9c1f7-e24b-4183-b9f0-9082e268578e) - partition WITHOUT quorum
Version: 1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd
2 Nodes configured, unknown expected votes
3 Resources configured.
============

Online: [ lb1 lb2 ]

 site_one_ip    (ocf::heartbeat:IPaddr):    Started lb1
 site_two_ip    (ocf::heartbeat:IPaddr):    Started lb2
 site_three_ip  (ocf::heartbeat:IPaddr):    Started lb1
ip failover heartbeat pacemaker

1 Answers

  1. Best Answer

    Whoever in curious to know if heartbeat with more than 2 node is possible, then I say heartbeat is not limited to 2 nodes we can join more than 2 nodes. Actually I didn't copy the same authkey for the 3rd node. All the three nodes is listing now.

    I Also tried Corosync, and one of the node I couldn't get online don't know why having all config and keys same, just started doubting the reliability of the Corosync which never happend in Heartbeat. Moreover, no support for Unicast in corosysnc didn't impress much.

    Thanks!

    • 2