Upgrade a Redis Enterprise Software cluster

Upgrade a Redis Enterprise Software cluster.

Supported upgrade paths

The following upgrade paths are supported:

cluster version
Upgrade to
cluster version
7.2.x 7.4.2
6.4.x 7.4.2
6.2.x 7.4.2
6.0.x 7.2.x

Upgrade prerequisites

Before upgrading a cluster:

  • Verify access to rlcheck and rladmin commands

  • Verify that you meet the upgrade path requirements for your desired cluster version and review the relevant release notes for any preparation instructions.

  • Upgrade the cluster's primary (master) node first. To identify the primary node, use one of the following methods:

Upgrade cluster

Starting with the primary (master) node, follow these steps for every node in the cluster. To ensure cluster availability, upgrade each node separately.

  1. Verify node operation with the following commands:

    $ rlcheck
    $ rladmin status extra all
  2. Download the Redis Enterprise Software installation package to the machine running the node from the Download Center on https://app.redislabs.com.

  3. Extract the installation package:

    tar vxf <tarfile name>
    You cannot change the installation path or the user during the upgrade.
  4. Run the install command. See installation script options for a list of command-line options you can add to the following command:

    sudo ./install.sh

    The installation script automatically recognizes the upgrade and responds accordingly.

    The upgrade replaces all node processes, which might briefly interrupt any active connections.

  5. Verify the node was upgraded to the new version and is still operational:

    $ rlcheck
    $ rladmin status extra all
  6. Visit the Cluster Manager UI.

    If the Cluster Manager UI was open in a web browser during the upgrade, refresh the browser to reload the console.

After all nodes are upgraded, the cluster is fully upgraded. Certain features introduced in the new version of Redis Enterprise Software only become available after upgrading the entire cluster.

After upgrading from version 6.0.x to 6.2.x, restart cnm_exec on each cluster node to enable more advanced state machine handling capabilities:

supervisorctl restart cnm_exec
Back to top ↑