升级集群的作系统

将 Redis Enterprise Software 集群的作系统升级到更高版本的主要版本。

Redis 企业软件

要将 Redis Enterprise Software 集群上的作系统 （OS） 升级到更高的主要版本，请执行滚动升级。由于您一次升级一个节点，因此您可以在不停机的情况下升级集群的作系统。

先决条件

在升级集群的作系统之前：

  1. 将集群中的所有节点升级到支持作系统当前版本和升级版本的 Redis Enterprise Software 版本。

    要了解哪些版本的 Redis Enterprise Software 支持特定的作系统版本，请参阅支持的平台。

  2. 如果集群包含任何使用模块的数据库：

    1. 在升级作系统之前，请将集群中的所有节点更新到 Redis Enterprise Software 版本 7.2.4-52 或更高版本。

    2. 使用rladmin:

      rladmin status modules

      The output lists the module versions installed on the cluster and the module versions used by existing databases:

      CLUSTER MODULES:
MODULE                                                                      VERSION                            
RedisBloom                                                                  2.6.3                              
RediSearch 2                                                                2.8.4                              
RedisGears                                                                  2.0.12                             
RedisGraph                                                                  2.10.12                            
RedisJSON                                                                   2.6.6                              
RedisTimeSeries                                                             1.10.6                             

DATABASE MODULES:
DB:ID    NAME       MODULE              VERSION     ARGS                     STATUS                            
db:1     db1        RediSearch 2        2.6.9       PARTITIONS AUTO          OK, OLD MODULE VERSION            
db:1     db1        RedisJSON           2.4.7                                OK, OLD MODULE VERSION

    3. Upload module packages for the target OS version to a node in the existing cluster. See Install a module on a cluster for instructions.

      Note:

      The uploaded module packages have the following requirements:

      • The module is compiled for the target OS version.

      • The module version matches the version currently used by databases.

  3. If the cluster uses custom directories, make sure the OS upgrade version also supports custom directories, and specify the same custom directories during installation for all nodes. See Customize installation directories for details.

Perform OS rolling upgrade

To upgrade the cluster's operating system, use one of the following rolling upgrade methods:

Extra node upgrade method

  1. Create a node with the OS upgrade version.

  2. Install the cluster's current Redis Enterprise Software version on the new node using the installation package for the OS upgrade version.

  3. Add the new node to the cluster.

  4. Remove one node running the earlier OS version from the cluster.

  5. Repeat the previous steps until all nodes with the earlier OS version are removed. If the final node to remove from the cluster is the primary node, demote it to a secondary node before you remove it.

Replace node upgrade method

  1. Remove a node with the earlier OS version from the cluster.

  2. Uninstall Redis Enterprise Software from the removed node:

    sudo ./rl_uninstall.sh

  3. Either upgrade the existing node to the OS upgrade version, or create a new node with the OS upgrade version.

  4. Install the cluster's current Redis Enterprise Software version on the upgraded node using the installation package for the OS upgrade version.

  5. Add the new node to the cluster.

    If you want to reuse the removed node's ID when you add the node to the cluster, run rladmin cluster join with the replace_node flag:

    rladmin cluster join nodes <cluster_member_ip_address> username <username> password <password> replace_node <node_id>

  6. Verify node health:

    1. Run rlcheck on all nodes:

      rlcheck

      The output lists the result of each verification test:

      ##### Welcome to Redis Enterprise Cluster settings verification utility ####
Running test: verify_bootstrap_status
                PASS
...
Running test: verify_encrypted_gossip
                PASS
Summary:
-------
ALL TESTS PASSED.

      For healthy nodes, the expected output is ALL TESTS PASSED.

    2. Run rladmin status on the new node:

      rladmin status extra all

      The expected output is the OK status for the cluster, nodes, endpoints, and shards:

      CLUSTER:
OK. Cluster master: 2 (<IP.address>)
Cluster health: OK, [0, 0.0, 0.0]
failures/minute - avg1 0.00, avg15 0.00, avg60 0.00.
...

  7. Repeat the previous steps until all nodes with the earlier OS version are replaced. If the final node to remove from the cluster is the primary node, demote it to a secondary node before you remove it.

RATE THIS PAGE
Back to top ↑