Documentation - Redise Pack

A guide to Redise Pack installation, operation and administration

open all | close all

Upgrading Redise Pack

Upgrading Redise Pack (RP) consists of upgrading the software on each of the nodes, in any order you wish.

To upgrade your cluster to v4.4 or before, you must first be on the immediately previous release. For example, to upgrade to 4.4, your cluster must already be on v4.3.

As of RP v4.5, you can upgrade from v4.4 or v4.3.

Note: A Redis Pack cluster upgrade is considered to be “ongoing” when nodes within a cluster have mixed versions. The upgrade is only considered complete when all nodes of the cluster are upgraded to the new version. Attempting to use newly added capabilities from the newer version of Redise Pack when the upgrade is ongoing, can produce unexpected results or cause failures in the cluster.

Upgrading nodes

Upgrading the nodes’ software requires installing the RP installation package on all of the machines on which RP is installed. For instructions, refer to Accessing and installing the setup package. You will run from the directory where you untarred the media just like you do for a new install. The software will recognize this is an upgrade and proceed accordingly.

Just like for a new installation, you must sudo to or be root to do the upgrade. $ sudo ./

During the node upgrade process, the services running RP are restarted. This will result in a very short interruption to the proxy and node itself and the databases running on it. This can be dramatically reduced by using multiple active proxies for your database. The client will lose the connection to the proxy on the node being upgraded, but then automatically reconnect to another active proxy you have configured for the database.

Note: In order to ensure cluster and databases’ availability, it is important to upgrade the nodes one by one, and not attempt to upgrade more than one node at a time.

It is highly advisable to run rlcheck and rladmin status extra all on the node both before and after the upgrade, to ensure that the node is functioning properly. For additional details, refer to rlcheck Installation Verification Utility.

If you have the RP management UI open in the browser while you are upgrading the nodes, ensure that you refresh the browser before trying to work with the UI again.

Upgrading databases

Some RP upgrades add support for new Redis versions. In these cases, Redis Labs recommends that you upgrade the databases to the new Redis version, although this is not mandatory because RP upgrades are backward compatible. RP also supports a mix of Redis database versions.

RP always supports two Redis versions. By default, new Redis databases are created with the latest version, and existing databases get upgraded to the latest version according to the instructions detailed below. If you would like to change the default Redis version to the previous version supported, you should use the tune cluster default_redis_version command in the rladmin CLI and set it to the previous Redis version supported.

To check whether your Redis database versions match the latest Redis version supported by RP:

  • In the rladmin CLI, run the status command (For additional details, refer to rladmin command-line interface (CLI)). If the Redis version is not the latest supported, an indication appears in the command output next to the database’s status.
  • In the Management UI, go to the Cluster > Configuration page. The page lists the latest Redis version supported.

If the Redis database versions are older than the version supported by RP, Redis Labs recommends that you upgrade your Redis databases.

To upgrade your database:

  1. Ensure that all of the nodes in the RP cluster have been upgraded, as described in Upgrading nodes section above. Otherwise, you will not be able to upgrade the databases.
  2. In the rladmin CLI, run the upgrade db command for each database. For additional details, refer to rladmin command-line interface (CLI).

During the database upgrade process, the database will be restarted. As a result:

  • For databases that have replication enabled (for additional details, refer to Database replication) a failover occurs prior to restarting the database to ensure that there is no downtime.
  • For databases that do not have replication enabled and persistence enabled, some downtime occurs while the database is restarting. The type of persistence chosen for this database is a variable in the time it will take for a database to come back up. For example, AOF usually takes longer than an RDB file.
  • For databases that have neither replication nor persistence enabled (for additional details, refer to Database persistence), the database loses all its data after it is restarted.