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:
2022-08-13 18:26:56

Active/Active HA configuration

In an active/active configuration, one node is active running one or more ResourceGroups, and the other node is also running one or more ResourceGroups.

The disadvantage of this configuration is that quality of service may be degraded when one machine runs both services. Additionally, resources are moved not only when machines fail, but when they return to service, resulting in twice as many service transitions as active/passive configurations.

The advantage of this configuration is that both nodes are providing useful service, and is generally viewed as a more efficient use of resources than an active/passive configuration.

To instruct Heartbeat to operate in active/active mode for Release 1 (non-CRM) clusters, simply make sure you configure the auto_failback directive in your file like this:

auto_failback on

This will ensure that both machines will run services according to the preferred host information in the haresources file.

Typically each ResourceGroup in the haresources file will need to include at least one ServiceAddress in it.

In release 2, simply create two groups, and Heartbeat will naturally schedule them in an active/active arrangement. The auto_failback directive only applies to R1-style haresources configurations, and should not be applied in R2 (CRM-based) configurations.

The corresponding attribute to put in the CIB is the resource_stickiness attribute.

See Also

Active/Passive HA configuration