Redis - Upgrade
PaaS upgrade workflow
Request
The update of a Redis PaaS is the responsibility of cegedim.cloud and can be requested via a request ticket submitted from ITCare.
Please specify a time slot to execute the upgrade and if the operation is to be carried out outside of business hours.
It is recommended that you upgrade your non-production environments first in order to estimate the downtime generated by the operation and to test your applications using the new engine version.
Process
The upgrade of a Redis deployment (single-instance or high availability cluster) takes place in two fully automated steps:
Update the operating system first if required
Multiple updates depending on the scenario: Debian 10 → Debian 11 → Debian 12
Update of the Redis and Sentinel engine in the specified target version
Depending on the source and target versions of Redis, it may be necessary to first migrate the operating system to a version supported by cegedim.cloud (for more information, check OS / Redis support matrix below).
Impacts
The duration of an update is variable and depends on:
The topology
Standalone topology: Redis will be upgraded.
Sentinel topology: Redis and Sentinel on all nodes will be upgraded.
The amount of operating system upgrade necessary
Time references
Debian operating system upgrade: 10 minutes on average
Redis package upgrade : 5 minutes on average
Sentinel package upgrade: 5 minutes on average
OS / Redis support matrix
Linux distributions supported by cegedim.cloud depending on the Redis version:
6.2.x
Debian 10
6.2.x
Debian 12 (deployments created after May 31, 2024)
7.2.x
Debian 12
OS upgrades is required only if the PaaS Redis 6.2 was provisionned before May 31, 2024. After this date, the Redis PaaS has been updated to be deployed on Debian 12.
Last updated