.
18 August 2008 Heartbeat release 2.1.4 is now out Download it and install it! |
11 October 2007 NEW educational HA/DR Blog hosted by Alan Robertson |
9 April 2007 Check out the Cool Heartbeat Screencasts: Installation, Intro to the GUI Part of the Heartbeat Education project |
Last site update:
2008-08-28 08:11:18
Upgrade Methodologies
There are three approaches to upgrading heartbeat:
Complete Cluster Shutdown
- In this scenario one shuts down all cluster nodes and resources and upgrades all the nodes before restarting the cluster.
Rolling (node by node)
- In this scenario each node is removed from the cluster, upgraded and then brought back online until all nodes are running the newest version.
Disconnect & Reattach
- A variant of a complete cluster shutdown, but the resources are left active and re-detected when the cluster is restarted.
Each method has advantages and disadvantages, some of which are listed in the table below:
Upgrade Type |
Version Issues |
Service Outage |
Recovery During Upgrade |
Exercises Fail-over Logic |
Shutdown |
no |
yes |
no |
no |
Rolling |
yes |
yes |
yes |
yes |
Reattach |
no |
no |
no |
no |
Version Compatibility
The stated goal of the Heartbeat team is to allow your cluster to be online for 100 years. As such, when releasing newer versions we take care to make sure we are backwardly compatible with older versions. While you will always be able to upgrade from version x to x+1, in order to continue to produce high quality software it may occasionally be necessary to drop compatibility with older versions.
There will always be an upgrade path from any series-2 release to any other series-2 release.
From time to time it is neccessary to perform some steps in addition to the usual upgrade procedure. You may want to check the UpdateExperience page to see some hints on those.
With the release of 2.0.5 we will be removing the ability to perform a rolling upgrade from any version lower than 2.0.4 in a single pass. However as noted above, other upgrade strategies exist and include the ability to upgrade without service interruption.
For those desperate to perform a rolling upgrade to 2.0.5 (and beyond) in a single pass, you will continue to be able to do so when compiling from scratch for some time yet as the relevant code has been disabled, not removed. Details are available on request.
Rolling Update Example: 2.0.1 to 2.0.6
Upgrading from 2.0.1 to 2.0.6:
Follow the rolling upgrade instructions to upgrade from 2.0.1 to 2.0.4
Follow the rolling upgrade instructions to upgrade from 2.0.4 to 2.0.6
Linux-HA site built by the Linux-HA crowd. HTML4 / CSS2 