Product SiteDocumentation Site

Appendix E. Upgrading Cluster Software

Table of Contents

E.1. Complete Cluster Shutdown
E.2. Rolling (node by node)
E.3. Disconnect and Reattach
There will always be an upgrade path from any pacemaker 1.x release to any other 1.y release.
Consult the documentation for your messaging layer (Heartbeat or Corosync) to see whether upgrading them to a newer version is also supported.
There are three approaches to upgrading your cluster software:
Each method has advantages and disadvantages, some of which are listed in the table below, and you should choose the one most appropriate to your needs.

Table E.1. Upgrade Methods

Type Available between all software versions Service Outage During Upgrade Service Recovery During Upgrade Exercises Failover Logic/Configuration Allows change of cluster stack type [a]
Shutdown
yes
always
N/A
no
yes
Rolling
no
always
yes
yes
no
Reattach
yes
only due to failure
no
no
yes
[a] For example, switching from Heartbeat to Corosync.

E.1. Complete Cluster Shutdown

In this scenario, one shuts down all cluster nodes and resources, then upgrades all the nodes before restarting the cluster.
  1. On each node:
    1. Shutdown the cluster software (pacemaker and the messaging layer).
    2. Upgrade the Pacemaker software. This may also include upgrading the messaging layer and/or the underlying operating system.
    3. Check the configuration manually or with the crm_verify tool if available.
  2. On each node:
    1. Start the cluster software. The messaging layer can be either Corosync or Heartbeat and does not need to be the same one before the upgrade.