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

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.

CRM Successor

Heartbeat 3.0

$/!\$ Pages linked to below may be out of date or right out obsolete.
See Site News.

Introduction

Using Linux-HA

Links

Common Searches

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-05-20 11:26:14

printer friendly view

Note

This page describes the release 1 architecture of the Linux-HA project. See the BasicArchitecture page for an overview of the release 2 architecture.

Technical Overview

The most well-known component of the Linux-HA project is Heartbeat. Heartbeat sends heartbeat packets across the network (or serial ports) to the other instances of Heartbeat as a sort of keep-alive message.

Heartbeat itself acts similar to a cluster-wide init daemon, making sure each of the services it manages are running at all times as though they were spawned with an init(8) respawn directive.

When heartbeat packets are no longer received, the node is assumed to be dead, and any services (resources) it was providing are failed over to the other node. This assumption of death can be assured to be true by the proper integration of STONITH or a watchdog timer.

Heartbeat can also monitor routers and switches as though they were cluster members using the ping or ping_group directives. Combined with the ipfail program, Heartbeat can also cause failovers when networking connectivity is compromised.

Heartbeat provides services (which it calls resources) as configured in the haresources file. The services in the haresources file are started in a left-to-right order, and stopped in a right-to-left order.

Communication

Heartbeat can communicate using a variety of mechanisms. It can communicate using any combination of UDP broadcast, UDP multicast, UDP unicast, and serial communication paths.

Heartbeat uses a multicast communications protocol to deal with lost and corrupted packets.

Note

Technical Overview

Communication

See Also