Highly available open source solution heartbeat vs keepalived

Ext.: http://www.kuqin.com/shuoit/20140623/340745.html

Recently, because of the project needs, a simple trial of two highly available open source solutions: keepalived and Heartbeat. Both are very popular, but the difference is still very large, will be the experience of the trial process and the relevant knowledge points a simple summary, for everyone to choose the plan when reference.

1)keepalived use more simple : From the installation, configuration, use, maintenance and other aspects of the comparison, keepalived is much simpler than heartbeat, especially Heartbeat2.1.4 split into 3 sub-projects, installation, configuration, Use is more complex, especially when the problem, do not know which subsystem is the problem, and keepalived only 1 installation files, a configuration file, configuration file is also much simpler;

2)heartbeat function more powerful : heartbeat Although complex, but more powerful, supporting tools more complete, suitable for large-scale cluster management, and keepalived mainly used for cluster switching, basically no management function;

3) The agreement is different : keepalived use VRRP protocol for communication and election, heartbeat use heartbeat for communication and election; Heartbeat in addition to the network, but also through the serial communication, seemingly more reliable;

4) use basically similar : If you want to design a high-availability scheme based on both, and ultimately to write customized scripts according to business needs, keepalived script without any constraints, any way to write it, heartbeat script is constrained, that is, to support service Start/stop/restart this way, and Heartbeart provides a lot of default scripts, simple binding IP, start Apache and other operations have been;

Usage advice: priority to use keepalived, when keepalived is not enough to choose heartbeat

Highly available open source solution heartbeat vs keepalived