升级 Redis Enterprise Software 集群
升级 Redis Enterprise Software 集群。
Redis 企业软件 |
---|
支持的升级路径
✅ 支持 – 您可以直接从当前的 Redis Software 集群版本升级。
❌ 不支持 – 您不能直接从当前的 Redis Software 集群版本升级。您必须先升级到受支持的中间版本。
当前 Redis Software 集群版本 | 升级到 Redis 软件 6.2.x | 升级到 Redis 软件 6.4.x | 升级到 Redis 软件 7.2.x | 升级到 Redis 软件 7.4.x | 升级到 Redis 软件 7.8.x |
---|---|---|---|---|---|
6.0.x 版本 | ✅ | ✅ | ✅ | ❌ | ❌ |
6.2.4 6.2.8 |
✅ | ✅ | ✅ | ✅ | ❌ |
6.2.10 6.2.12 6.2.18 |
✅ | ✅ | ✅ | ✅ | ✅ |
6.4.x | – | ✅ | ✅ | ✅ | ✅ |
7.2.x 版本 | – | – | ✅ | ✅ | ✅ |
7.4.x 版本 | – | – | – | ✅ | ✅ |
有关版本号和生命周期终止计划的更多信息,请参阅 Redis Enterprise Software 产品生命周期。
升级先决条件
升级集群前:
-
验证您是否满足所需集群版本的升级路径要求,并查看相关的发行说明以获取任何准备说明。
-
避免在升级过程中更改数据库配置或执行其他集群管理作,因为这可能会导致意外结果。
-
首先升级集群的主(主)节点。要识别主节点,请使用以下方法之一:
-
新集群管理器 UI 中的节点屏幕(仅适用于 Redis Enterprise 版本 7.2 及更高版本)
-
GET /nodes/status
REST API 请求
-
升级集群
从主(主)节点开始,对集群中的每个节点执行以下步骤。为保证集群可用性,请分别升级每个节点。
-
使用以下命令验证节点作:
$ rlcheck $ rladmin status extra all
-
Download the Redis Enterprise Software installation package to the machine running the node from the Download Center on https://cloud.redis.io.
-
Extract the installation package:
tar vxf <tarfile name>
Note:You cannot change the installation path or the user during the upgrade. -
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.
-
Verify the node was upgraded to the new version and is still operational:
$ rlcheck $ rladmin status extra all
-
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
On this page