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

Homepage

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:
2017-12-13 22:10:50

Rolling Upgrade

A Rolling Upgrade is an upgrade which proceeds through a cluster one node at a time. The fundamental rule of a Rolling Upgrade is that the cluster as a whole is never shut down. That is, even though individual machines are rebooted, or services migrated from one machine to another, the cluster itself never stops providing service.

Small service interruptions may be observed, but since the cluster as a whole never shuts down, service remains basically uninterrupted throughout the upgrade process. During a Rolling Upgrade, all resources remain at all times under the supervision of the LocalResourceManager and the ClusterResourceManager.

This is the model which Heartbeat has used for all its upgrades up until the present time.

This is several steps short of the more complex and risky TransparentUpgrade -- in which no service interruption is visible at all, but the resources run for period of time not under supervision.

See Also

TransparentUpgrade