LinuxWorld

High availability and Heartbeat

We mentioned Heartbeat a couple of columns ago when we started on Linux Enterprise Clusters, so let's dig deeper.

Heartbeat is a subsystem that allows a primary and a back-up Linux server to determine if the other is "alive" and if the primary isn't, fail over resources to the backup. Heartbeat uses inter-server signaling called "heartbeats" over serial, User Datagram Protocol and PPP/UDP connections, and handles the process of the transfer of the server's IP addresses.

Heartbeat arose from the Heart project in 1999 and is one of the foundational technologies of the High Availability Linux Project.

Now, as simple as failover might sound, we're talking computers and networking and so, of course, it isn't. In fact, the problem is so complex that the current release only supports a pair of nodes. This will change with the forthcoming release of HA Linux Release 2 (HAL-R2) within the next couple of months.

HAL-R2 will be a major revision of the entire Linux system. HAL-R2 will extend Heartbeat's functionality to support multiple nodes, the ability to monitor resources for correct operation, and support for configuration dependencies.

Being able to support multiple nodes in a cluster is crucial, as is monitoring. Resource monitoring ensures that the failure of a service provided by a node can be detected even without the node actually "dying."

Dependencies, otherwise called "constraints" are important, as you might never want database servers to run on the same node as Web servers, or you might want to always have data replication services run only on nodes that are running the database services.

The version of Heartbeat available today is a stable and effective way of ensuring that two nodes in a cluster act in a coordinated manner. Each server runs the Heartbeat daemon and exchange messages called Heartbeats that inform the other machine that the sender is alive.

In the event of the primary node failing, the back-up node Heartbeat is responsible for transferring any IP addresses that must be available after failover.

React: Give us your thoughts on the issues here.
Use this form to start a public discussion with other Linux World users on this article.
Log In | Register for an account (Why you should)

Note: Register to have your user name appear; otherwise your comment will show up as "Anonymous."

*Anonymous comments will only appear once they are approved by the moderator.

Newsletter sign-up

Sign up for one of Network World's newsletters compliments of Linux World

Linux & Open Source News Alert
Web Applications Alert
Video & Podcast Alert
Security: Threat  Alert
Virtualization Alert

Email Address: