This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag


About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2019-12-06 10:48:06

CCM does not handle partitions merge well so far. Here is one way to handle it.


CCM states are categorized as two classes:


If a node is in first class, it is not considered as part of the cluster yet and it will not join the cluster until a leader is elected.

2) other states.

How to distingish partitions merge from a fresh new node join

If the joined node is in class 1) state, it is a new one, otherwise it is from another partition.

CCM needs to be able to communicate with each other with info that it is in class 1) or class 2) states

How does merge happen?

We received a node join message:

if (fresh_new_join){
  /*do nothing
   *the fresh new joined node will initiate the join protocol
}else {
/* it is  partition merge*/
send out joining message to start join protocol