Pacemaker achieves maximum availability for cluster services by detecting and recovering from node and service-level failures. It achieves this by utilizing the messaging and membership capabilities provided by your preferred cluster infrastructure (currently either OpenAIS or Heartbeat).

learn more… | top users | synonyms

13
votes
7answers
16k views

Alternatives to Heartbeat, Pacemaker and CoroSync?

Are there any major alternatives for automatic failover on Linux besides the typical Heartbeat/Pacemaker/CoroSync combinations? In particular, I'm setting up failover on EC2 instances, which only ...
3
votes
3answers
2k views

Do Pacemaker, Heartbeat, etc. make sense for EC2?

Does the Pacemaker ecosystem (Corosync etc.) make sense in the context of EC2? Up till some point, Corosync required IP multicast (not available on EC2), but I think it has broadcast now. Still, are ...
3
votes
1answer
2k views

Secure IPTables rules for Corosync

I have two HA load balancers (hollywood and wolfman) running Corosync and Pacemaker. The eth1 interfaces are connected to the WAN, and the eth0 interfaces to the LAN, using a virtual IP as the gateway ...
3
votes
1answer
1k views

Heartbeat Pacemaker 3 node/ip failover

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 ...