################################ REDIS CLUSTER  ###############################

# Normal Redis instances can't be part of a Redis Cluster; only nodes that are
# started as cluster nodes can. In order to start a Redis instance as a
# cluster node enable the cluster support uncommenting the following:
#
# cluster-enabled yes #启用Cluster模式

# Every cluster node has a cluster configuration file. This file is not
# intended to be edited by hand. It is created and updated by Redis nodes.
# Every Redis Cluster node requires a different cluster configuration file.
# Make sure that instances running in the same system do not have
# overlapping cluster configuration file names.
#
# cluster-config-file nodes-6379.conf #Cluster节点配置文件名称

# Cluster node timeout is the amount of milliseconds a node must be unreachable
# for it to be considered in failure state.
# Most other internal time limits are multiple of the node timeout.
#
# cluster-node-timeout 15000 #Cluster节点超时时间，单位：毫秒

# A replica of a failing master will avoid to start a failover if its data
# looks too old.
#
# There is no simple way for a replica to actually have an exact measure of
# its "data age", so the following two checks are performed:
#
# 1) If there are multiple replicas able to failover, they exchange messages
#    in order to try to give an advantage to the replica with the best
#    replication offset (more data from the master processed).
#    Replicas will try to get their rank by offset, and apply to the start
#    of the failover a delay proportional to their rank.
#
# 2) Every single replica computes the time of the last interaction with
#    its master. This can be the last ping or command received (if the master
#    is still in the "connected" state), or the time that elapsed since the
#    disconnection with the master (if the replication link is currently down).
#    If the last interaction is too old, the replica will not try to failover
#    at all.
#
# The point "2" can be tuned by user. Specifically a replica will not perform
# the failover if, since the last interaction with the master, the time
# elapsed is greater than:
#
#   (node-timeout * replica-validity-factor) + repl-ping-replica-period
#
# So for example if node-timeout is 30 seconds, and the replica-validity-factor
# is 10, and assuming a default repl-ping-replica-period of 10 seconds, the
# replica will not try to failover if it was not able to talk with the master
# for longer than 310 seconds.
#
# A large replica-validity-factor may allow replicas with too old data to failover
# a master, while a too small value may prevent the cluster from being able to
# elect a replica at all.
#
# For maximum availability, it is possible to set the replica-validity-factor
# to a value of 0, which means, that replicas will always try to failover the
# master regardless of the last time they interacted with the master.
# (However they'll always try to apply a delay proportional to their
# offset rank).
#
# Zero is the only value able to guarantee that when all the partitions heal
# the cluster will always be able to continue.
#
# cluster-replica-validity-factor 10
# 集群副本有效性因子（0表示slave将始终尝试故障转移为master，默认被注释掉）
# (node-timeout * replica-validity-factor) + repl-ping-replica-period
# 计算时间（秒），如果slave无法与master通信的时间超过了该时间，则slave将不会尝试故障转移

# Cluster replicas are able to migrate to orphaned masters, that are masters
# that are left without working replicas. This improves the cluster ability
# to resist to failures as otherwise an orphaned master can't be failed over
# in case of failure if it has no working replicas.
#
# Replicas migrate to orphaned masters only if there are still at least a
# given number of other working replicas for their old master. This number
# is the "migration barrier". A migration barrier of 1 means that a replica
# will migrate only if there is at least 1 other working replica for its master
# and so forth. It usually reflects the number of replicas you want for every
# master in your cluster.
#
# Default is 1 (replicas migrate only if their masters remain with at least
# one replica). To disable migration just set it to a very large value.
# A value of 0 can be set but is useful only for debugging and dangerous
# in production.
#
# cluster-migration-barrier 1 #集群迁移屏障，仅当master至少有1个其他工作副本时，副本才会迁移

# By default Redis Cluster nodes stop accepting queries if they detect there
# is at least an hash slot uncovered (no available node is serving it).
# This way if the cluster is partially down (for example a range of hash slots
# are no longer covered) all the cluster becomes, eventually, unavailable.
# It automatically returns available as soon as all the slots are covered again.
#
# However sometimes you want the subset of the cluster which is working,
# to continue to accept queries for the part of the key space that is still
# covered. In order to do so, just set the cluster-require-full-coverage
# option to no.
#
# cluster-require-full-coverage yes # 集群需要全覆盖（默认为 yes，被注释掉）
# 如果redis集群节点检测到至少有一个未覆盖的哈希槽（没有可用的节点提供服务），则会停止接受查询
# 如果集群部分关闭（例如不再覆盖一系列哈希槽），整个集群将不可用
# 当所有插槽再次被覆盖，集群将自动返回可用状态

# This option, when set to yes, prevents replicas from trying to failover its
# master during master failures. However the master can still perform a
# manual failover, if forced to do so.
#
# This is useful in different scenarios, especially in the case of multiple
# data center operations, where we want one side to never be promoted if not
# in the case of a total DC failure.
#
# cluster-replica-no-failover no #主节点故障期间不启用故障转移

# In order to setup your cluster make sure to read the documentation
# available at http://redis.io web site.

########################## CLUSTER DOCKER/NAT support  ########################

# In certain deployments, Redis Cluster nodes address discovery fails, because
# addresses are NAT-ted or because ports are forwarded (the typical case is
# Docker and other containers).
#
# In order to make Redis Cluster working in such environments, a static
# configuration where each node knows its public address is needed. The
# following two options are used for this scope, and are:
#
# * cluster-announce-ip
# * cluster-announce-port
# * cluster-announce-bus-port
#
# Each instruct the node about its address, client port, and cluster message
# bus port. The information is then published in the header of the bus packets
# so that other nodes will be able to correctly map the address of the node
# publishing the information.
#
# If the above options are not used, the normal Redis Cluster auto-detection
# will be used instead.
#
# Note that when remapped, the bus port may not be at the fixed offset of
# clients port + 10000, so you can specify any port and bus-port depending
# on how they get remapped. If the bus-port is not set, a fixed offset of
# 10000 will be used as usually.
#
# Example:
#
# cluster-announce-ip 10.1.1.5
# cluster-announce-port 6379
# cluster-announce-bus-port 6380
# 配置集群节点的公共地址（默认被注释掉，使用redis群集自动检测）
# 节点的ip地址，客户端端口，集群消息总线端口

[root@Redis-Ubuntu1804-node1:~]# apt install redis -y
[root@Redis-Ubuntu1804-node1:~]# sed -i.bak -e 's/bind 127.0.0.1/bind 0.0.0.0/' -e '/masterauth/a masterauth redis' -e '/# requirepass/a requirepass redis' -e '/# cluster-enabled yes/a cluster-enabled yes' -e '/# cluster-config-file/a cluster-config-file nodes-6379.conf' -e '/# cluster-require-full-coverage yes/a cluster-require-full-coverage yes' /etc/redis/redis.conf
[root@Redis-Ubuntu1804-node1:~]# systemctl restart redis
[root@Redis-Ubuntu1804-node1:~]# ss -ntl
State             Recv-Q             Send-Q                          Local Address:Port                           Peer Address:Port             
LISTEN            0                  128                             127.0.0.53%lo:53                                  0.0.0.0:*                
LISTEN            0                  128                                   0.0.0.0:22                                  0.0.0.0:*                
LISTEN            0                  128                                 127.0.0.1:6010                                0.0.0.0:*                
LISTEN            0                  128                                   0.0.0.0:16379                               0.0.0.0:*                
LISTEN            0                  128                                   0.0.0.0:6379                                0.0.0.0:*                
LISTEN            0                  128                                      [::]:22                                     [::]:*                
LISTEN            0                  128                                     [::1]:6010                                   [::]:*                
[root@Redis-Ubuntu1804-node1:~]# ps -ef | grep redis
redis      2098      1  0 01:38 ?        00:00:00 /usr/bin/redis-server 0.0.0.0:6379 [cluster]
root       2112   1236  0 01:39 pts/0    00:00:00 grep --color=auto redis
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster nodes
98bb2740b622645ff51fd07bc994bb22e94feaaa :6379@16379 myself,master - 0 0 0 connected
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.20 6379
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.20 6379
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.21 6379
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.22 6379
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.30 6379
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.31 6379
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster meet 10.0.0.32 6379
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster nodes
98bb2740b622645ff51fd07bc994bb22e94feaaa 10.0.0.20:6379@16379 myself,master - 0 1681926433000 1 connected
9fe09d53d884c6c99c926a0e7213cf5386987ebf 10.0.0.32:6379@16379 master - 0 1681926434205 5 connected
55fd3a5d21e026b6503a89f1d88996b2a67c314a 10.0.0.31:6379@16379 master - 0 1681926435212 4 connected
6717c6b5a6170963ac251a1f14b0c600e917aa26 10.0.0.30:6379@16379 master - 0 1681926433000 3 connected
d9c17ded7fb139f9eb7fd41e476bb8e17c8b9bed 10.0.0.21:6379@16379 master - 0 1681926434000 0 connected
bdec3c92bcaa00c8ad1850cd477eb0a8f8a28aa2 10.0.0.22:6379@16379 master - 0 1681926433199 2 connected
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster info
cluster_state:fail
cluster_slots_assigned:0
cluster_slots_ok:0
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:0
cluster_current_epoch:5
cluster_my_epoch:1
cluster_stats_messages_ping_sent:70
cluster_stats_messages_pong_sent:89
cluster_stats_messages_meet_sent:6
cluster_stats_messages_sent:165
cluster_stats_messages_ping_received:88
cluster_stats_messages_pong_received:76
cluster_stats_messages_meet_received:1
cluster_stats_messages_received:165
[root@Redis-Ubuntu1804-node1:~]# 

[root@Client-Ubuntu-1804-250:~/script/redis]# cat add_slots.sh 
#!/bin/bash
#
#********************************************************************
#Author:                janzen
#Date:                  2023-04-20
#FileName：             add_slots.sh
#Description：          The test script
#Copyright (C):        2023 All rights reserved
#********************************************************************
host=$1
port=$2
start=$3
end=$4
passwd=redis

for slot in `seq $start $end`; do
    redis-cli -h $host -p $port -a $passwd --no-auth-warning cluster addslots $slot &&
    echo $slot add to node $host:$port
done
[root@Client-Ubuntu-1804-250:~/script/redis]# 
[root@Client-Ubuntu-1804-250:~/script/redis]# ./add_slots.sh 10.0.0.20 6379 0 5460 >> addslot.log
[root@Client-Ubuntu-1804-250:~/script/redis]# ./add_slots.sh 10.0.0.21 6379 5461 10922 >> addslot.log
[root@Client-Ubuntu-1804-250:~/script/redis]# ./add_slots.sh 10.0.0.22 6379 10923 16383 >> addslot.log

##查看当前集群信息，槽位已完成分配
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster nodes
98bb2740b622645ff51fd07bc994bb22e94feaaa 10.0.0.20:6379@16379 myself,master - 0 1681929286000 1 connected 0-5460
55fd3a5d21e026b6503a89f1d88996b2a67c314a 10.0.0.31:6379@16379 master - 0 1681929287000 4 connected
9fe09d53d884c6c99c926a0e7213cf5386987ebf 10.0.0.32:6379@16379 master - 0 1681929287000 5 connected
6717c6b5a6170963ac251a1f14b0c600e917aa26 10.0.0.30:6379@16379 master - 0 1681929288247 3 connected
d9c17ded7fb139f9eb7fd41e476bb8e17c8b9bed 10.0.0.21:6379@16379 master - 0 1681929286000 0 connected 5461-10922
bdec3c92bcaa00c8ad1850cd477eb0a8f8a28aa2 10.0.0.22:6379@16379 master - 0 1681929289256 2 connected 10923-16383
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.30 cluster replicate 98bb2740b622645ff51fd07bc994bb22e94feaaa
OK

##观察主节点上的replication信息
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 info Replication
# Replication
role:master
connected_slaves:1
slave0:ip=10.0.0.30,port=6379,state=online,offset=350,lag=1
master_replid:6a823070fcbc13b4f4eb7b5d13bf1d2f4625a1a2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:350
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:350
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 cluster nodes
98bb2740b622645ff51fd07bc994bb22e94feaaa 10.0.0.20:6379@16379 myself,master - 0 1681929989000 1 connected 0-5460
55fd3a5d21e026b6503a89f1d88996b2a67c314a 10.0.0.31:6379@16379 master - 0 1681929992372 4 connected
9fe09d53d884c6c99c926a0e7213cf5386987ebf 10.0.0.32:6379@16379 master - 0 1681929991000 5 connected
6717c6b5a6170963ac251a1f14b0c600e917aa26 10.0.0.30:6379@16379 slave 98bb2740b622645ff51fd07bc994bb22e94feaaa 0 1681929992000 3 connected
d9c17ded7fb139f9eb7fd41e476bb8e17c8b9bed 10.0.0.21:6379@16379 master - 0 1681929989351 0 connected 5461-10922
bdec3c92bcaa00c8ad1850cd477eb0a8f8a28aa2 10.0.0.22:6379@16379 master - 0 1681929991364 2 connected 10923-16383

##观察从节点上的replication信息
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.30 info Replication
# Replication
role:slave
master_host:10.0.0.20
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:462
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:6a823070fcbc13b4f4eb7b5d13bf1d2f4625a1a2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:462
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:462
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.31 cluster replicate d9c17ded7fb139f9eb7fd41e476bb8e17c8b9bed
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.32 cluster replicate bdec3c92bcaa00c8ad1850cd477eb0a8f8a28aa2
OK

##观察集群节点状态
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.30 cluster nodes
9fe09d53d884c6c99c926a0e7213cf5386987ebf 10.0.0.32:6379@16379 slave bdec3c92bcaa00c8ad1850cd477eb0a8f8a28aa2 0 1681930655876 5 connected
98bb2740b622645ff51fd07bc994bb22e94feaaa 10.0.0.20:6379@16379 master - 0 1681930654870 1 connected 0-5460
55fd3a5d21e026b6503a89f1d88996b2a67c314a 10.0.0.31:6379@16379 slave d9c17ded7fb139f9eb7fd41e476bb8e17c8b9bed 0 1681930656886 4 connected
bdec3c92bcaa00c8ad1850cd477eb0a8f8a28aa2 10.0.0.22:6379@16379 master - 0 1681930655000 2 connected 10923-16383
6717c6b5a6170963ac251a1f14b0c600e917aa26 10.0.0.30:6379@16379 myself,slave 98bb2740b622645ff51fd07bc994bb22e94feaaa 0 1681930654000 3 connected
d9c17ded7fb139f9eb7fd41e476bb8e17c8b9bed 10.0.0.21:6379@16379 master - 0 1681930653863 0 connected 5461-10922

[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.20 set node1 10.0.0.20
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.21 set node2 10.0.0.21
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.22 set node3 10.0.0.22
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.30 set node5 10.0.0.24
OK
[root@Redis-Ubuntu1804-node1:~]# 
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.31 get node1
"10.0.0.20"
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.31 get node2
"10.0.0.21"
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c -a redis -h 10.0.0.21 get node6
"10.0.0.31"
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node3:~]# redis-cli -a redis --cluster help
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Cluster Manager Commands:
  create         host1:port1 ... hostN:portN　　　　##创建集群
                 --cluster-replicas <arg>　　　　##指定每个集群的slave节点数，通常为1
  check          host:port　　　　##检查集群信息
                 --cluster-search-multiple-owners
  info           host:port　　　　##查看集群节点基本信息
  fix            host:port　　　　##修复集群
                 --cluster-search-multiple-owners
  reshard        host:port　　　　##在线热机迁移指定的slots数据
                 --cluster-from <arg>
                 --cluster-to <arg>
                 --cluster-slots <arg>
                 --cluster-yes
                 --cluster-timeout <arg>
                 --cluster-pipeline <arg>
                 --cluster-replace
  rebalance      host:port　　　　##平衡集群在线节点的slots数量
                 --cluster-weight <node1=w1...nodeN=wN>
                 --cluster-use-empty-masters
                 --cluster-timeout <arg>
                 --cluster-simulate
                 --cluster-pipeline <arg>
                 --cluster-threshold <arg>
                 --cluster-replace
  add-node       new_host:new_port existing_host:existing_port　　　　##添加新的节点到集群中
                 --cluster-slave
                 --cluster-master-id <arg>
  del-node       host:port node_id　　　　##删除集群中的节点
  call           host:port command arg arg .. arg　　　　##在集群上的所有节点执行命令
  set-timeout    host:port milliseconds　　　　##设置节点超时时间
  import         host:port　　　　##导入外部redis数据到当前集群
                 --cluster-from <arg>
                 --cluster-copy
                 --cluster-replace
  help           

For check, fix, reshard, del-node, set-timeout you can specify the host and port of any working node in the cluster.

[root@Redis-Ubuntu1804-node4:~]# redis-cli -a redis --version
redis-cli 5.0.14
[root@Redis-Ubuntu1804-node4:~]# redis-cli -a redis --no-auth-warning cluster nodes
e603091426e2ce29629ca51fb5e7dafb2f0c9524 :6379@16379 myself,master - 0 0 0 connected
[root@Redis-Ubuntu1804-node4:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --cluster create 10.0.0.20:6379 10.0.0.21:6379 10.0.0.22:6379 10.0.0.30:6379 10.0.0.31:6379 10.0.0.32:6379 --cluster-replicas 1
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 10.0.0.31:6379 to 10.0.0.20:6379
Adding replica 10.0.0.32:6379 to 10.0.0.21:6379
Adding replica 10.0.0.30:6379 to 10.0.0.22:6379
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
M: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots:[10923-16383] (5461 slots) master
S: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   replicates 07a36af61eb1f887419f2266b2360b4f795bb7a3
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
S: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 07a36af61eb1f887419f2266b2360b4f795bb7a3
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis cluster nodes
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 master - 0 1681998239529 3 connected 10923-16383
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1681998238520 2 connected 5461-10922
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1681998237000 6 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1681998238000 5 connected
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 slave 07a36af61eb1f887419f2266b2360b4f795bb7a3 0 1681998237510 4 connected
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 myself,master - 0 1681998236000 1 connected 0-5460
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis cluster info
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:290
cluster_stats_messages_pong_sent:282
cluster_stats_messages_sent:572
cluster_stats_messages_ping_received:277
cluster_stats_messages_pong_received:290
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:572
[root@Redis-Ubuntu1804-node1:~]# 
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (07a36af6...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (07a36af6...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
S: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 07a36af61eb1f887419f2266b2360b4f795bb7a3
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning cluster nodes
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 master - 0 1681998730094 3 connected 10923-16383
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1681998729087 2 connected 5461-10922
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1681998728000 6 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1681998728079 5 connected
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 slave 07a36af61eb1f887419f2266b2360b4f795bb7a3 0 1681998729000 4 connected
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 myself,master - 0 1681998726000 1 connected 0-5460
#写入 key1：value1
###经过slot计算 key1 不属于当前节点
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning set key1 value1
(error) MOVED 9189 10.0.0.21:6379
##计算 key 值所属的slot号
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning cluster keyslot key1
(integer) 9189
##结合 nodes 信息，切换到对应节点上进行写入
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.21 --no-auth-warning set key1 value1
OK
##get命令也只可查看当前节点上的数据
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning get key1
(error) MOVED 9189 10.0.0.21:6379
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.21 --no-auth-warning get key1
"value1"

##可以用 -c 参数通过连接到集群进行数据操作，就无需反复切换节点（key1、key4 不在当前节点所属的slot范围，出现错误提示）
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning cluster keyslot key1
(integer) 9189
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning cluster keyslot key2
(integer) 4998
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning cluster keyslot key3
(integer) 935
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning cluster keyslot key4
(integer) 13120
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.21 --no-auth-warning set key1 value1
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning set key1 value1
(error) MOVED 9189 10.0.0.21:6379
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning set key2 value2
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning set key3 value3
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --no-auth-warning set key4 value4
(error) MOVED 13120 10.0.0.22:6379
[root@Redis-Ubuntu1804-node1:~]#

##使用 -c 参数后执行成功
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning set key1 value1
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning set key4 value4
OK
[root@Redis-Ubuntu1804-node1:~]#

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning cluster nodes
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 master - 0 1681999895495 3 connected 10923-16383
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1681999896502 2 connected 5461-10922
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1681999894488 6 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1681999895000 5 connected
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 slave 07a36af61eb1f887419f2266b2360b4f795bb7a3 0 1681999892000 4 connected
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 myself,master - 0 1681999893000 1 connected 0-5460
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 97 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (07a36af6...) -> 100 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 92 keys | 5462 slots | 1 slaves.
[OK] 289 keys in 3 masters.
0.02 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 99 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (07a36af6...) -> 103 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 94 keys | 5462 slots | 1 slaves.
[OK] 296 keys in 3 masters.
0.02 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
S: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 07a36af61eb1f887419f2266b2360b4f795bb7a3
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node3:~]# systemctl stop redis_6379.service 
[root@Redis-Ubuntu1804-node3:~]# 

##10.0.0.22节点标记 faild，并提升它的从节点 10.0.0.30 为master
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
Could not connect to Redis at 10.0.0.22:6379: Connection refused
*** WARNING: 10.0.0.30:6379 claims to be slave of unknown node ID 07a36af61eb1f887419f2266b2360b4f795bb7a3.
10.0.0.20:6379 (6b142fe3...) -> 131 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 126 keys | 5462 slots | 1 slaves.
[OK] 257 keys in 2 masters.
0.02 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
S: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 07a36af61eb1f887419f2266b2360b4f795bb7a3
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[ERR] Not all 16384 slots are covered by nodes.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
Could not connect to Redis at 10.0.0.22:6379: Connection refused
*** WARNING: 10.0.0.30:6379 claims to be slave of unknown node ID 07a36af61eb1f887419f2266b2360b4f795bb7a3.
10.0.0.20:6379 (6b142fe3...) -> 131 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 126 keys | 5462 slots | 1 slaves.
[OK] 257 keys in 2 masters.
0.02 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning cluster nodes
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 master,fail - 1682000024732 1682000022415 3 disconnected
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1682000042000 2 connected 5461-10922
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1682000040567 6 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1682000042582 5 connected
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 master - 0 1682000041575 7 connected 10923-16383
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 myself,master - 0 1682000041000 1 connected 0-5460
[root@Redis-Ubuntu1804-node1:~]# 

17519:M 20 Apr 2023 22:14:01.600 * Marking node 07a36af61eb1f887419f2266b2360b4f795bb7a3 as failing (quorum reached).
17519:M 20 Apr 2023 22:14:01.600 # Cluster state changed: fail
17519:M 20 Apr 2023 22:14:02.167 # Failover auth granted to 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 for epoch 7
17519:M 20 Apr 2023 22:14:02.177 # Cluster state changed: ok

##10.0.0.22节点被添加为slave节点，并将master指向10.0.0.30
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 150 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 141 keys | 5462 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 154 keys | 5461 slots | 1 slaves.
[OK] 445 keys in 3 masters.
0.03 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 150 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 141 keys | 5462 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 154 keys | 5461 slots | 1 slaves.
[OK] 445 keys in 3 masters.
0.03 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

##日志记录清除 10.0.0.22 节点上的faild 标记，并作为slave节点启动
17519:M 20 Apr 2023 22:14:01.600 * Marking node 07a36af61eb1f887419f2266b2360b4f795bb7a3 as failing (quorum reached).
17519:M 20 Apr 2023 22:14:01.600 # Cluster state changed: fail
17519:M 20 Apr 2023 22:14:02.167 # Failover auth granted to 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 for epoch 7
17519:M 20 Apr 2023 22:14:02.177 # Cluster state changed: ok
17519:M 20 Apr 2023 22:17:23.792 * Clear FAIL state for node 07a36af61eb1f887419f2266b2360b4f795bb7a3: master without slots is reachable again.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis cluster nodes
1c2fee65ee50cdf66c862d04710672286b305f55 :6379@16379 myself,master - 0 0 0 connected
[root@Redis-Ubuntu1804-node1:~]# redis-cli --version
redis-cli 4.0.9
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# find / -name redis-trib.rb
/usr/share/doc/redis-tools/examples/redis-trib.rb
[root@Redis-Ubuntu1804-node1:~]# cp /usr/share/doc/redis-tools/examples/redis-trib.rb /usr/bin/

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb 
/usr/bin/env: ‘ruby’: No such file or directory
[root@Redis-Ubuntu1804-node1:~]# ruby

Command 'ruby' not found, but can be installed with:

snap install ruby  # version 3.2.2, or
apt  install ruby

See 'snap info ruby' for additional versions.

[root@Redis-Ubuntu1804-node1:~]# apt-cache madison ruby
      ruby |    1:2.5.1 | http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
[root@Redis-Ubuntu1804-node1:~]# apt install ruby -y
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.15.0-151 linux-headers-4.15.0-151-generic linux-image-4.15.0-151-generic linux-modules-4.15.0-151-generic
  linux-modules-extra-4.15.0-151-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  fonts-lato javascript-common libjs-jquery libruby2.5 rake ruby-did-you-mean ruby-minitest ruby-net-telnet ruby-power-assert ruby-test-unit
  ruby2.5 rubygems-integration unzip zip
Suggested packages:
  apache2 | lighttpd | httpd ri ruby-dev bundler
The following NEW packages will be installed:
  fonts-lato javascript-common libjs-jquery libruby2.5 rake ruby ruby-did-you-mean ruby-minitest ruby-net-telnet ruby-power-assert
  ruby-test-unit ruby2.5 rubygems-integration unzip zip
0 upgraded, 15 newly installed, 0 to remove and 62 not upgraded.
Need to get 6499 kB of archives.
After this operation, 29.0 MB of additional disk space will be used.
Get:1 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 fonts-lato all 2.0-2 [2698 kB]
Get:2 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 javascript-common all 11 [6066 B]
Get:3 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 libjs-jquery all 3.2.1-1 [152 kB]
Get:4 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 rubygems-integration all 1.11 [4994 B]
Get:5 http://cn.archive.ubuntu.com/ubuntu bionic-updates/main amd64 ruby2.5 amd64 2.5.1-1ubuntu1.13 [48.6 kB]
Get:6 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 ruby amd64 1:2.5.1 [5712 B]
Get:7 http://cn.archive.ubuntu.com/ubuntu bionic-updates/main amd64 rake all 12.3.1-1ubuntu0.1 [44.9 kB]
Get:8 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 ruby-did-you-mean all 1.2.0-2 [9700 B]
Get:9 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 ruby-minitest all 5.10.3-1 [38.6 kB]
Get:10 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 ruby-net-telnet all 0.1.1-2 [12.6 kB]
Get:11 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 ruby-power-assert all 0.3.0-1 [7952 B]
Get:12 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 ruby-test-unit all 3.2.5-1 [61.1 kB]
Get:13 http://cn.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libruby2.5 amd64 2.5.1-1ubuntu1.13 [3074 kB]                              
Get:14 http://cn.archive.ubuntu.com/ubuntu bionic-updates/main amd64 unzip amd64 6.0-21ubuntu1.2 [168 kB]                                      
Get:15 http://cn.archive.ubuntu.com/ubuntu bionic/main amd64 zip amd64 3.0-11build1 [167 kB]                                                   
Fetched 6499 kB in 9s (722 kB/s)                                                                                                               
Selecting previously unselected package fonts-lato.
(Reading database ... 144903 files and directories currently installed.)
Preparing to unpack .../00-fonts-lato_2.0-2_all.deb ...
Unpacking fonts-lato (2.0-2) ...
Selecting previously unselected package javascript-common.
Preparing to unpack .../01-javascript-common_11_all.deb ...
Unpacking javascript-common (11) ...
Selecting previously unselected package libjs-jquery.
Preparing to unpack .../02-libjs-jquery_3.2.1-1_all.deb ...
Unpacking libjs-jquery (3.2.1-1) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../03-rubygems-integration_1.11_all.deb ...
Unpacking rubygems-integration (1.11) ...
Selecting previously unselected package ruby2.5.
Preparing to unpack .../04-ruby2.5_2.5.1-1ubuntu1.13_amd64.deb ...
Unpacking ruby2.5 (2.5.1-1ubuntu1.13) ...
Selecting previously unselected package ruby.
Preparing to unpack .../05-ruby_1%3a2.5.1_amd64.deb ...
Unpacking ruby (1:2.5.1) ...
Selecting previously unselected package rake.
Preparing to unpack .../06-rake_12.3.1-1ubuntu0.1_all.deb ...
Unpacking rake (12.3.1-1ubuntu0.1) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../07-ruby-did-you-mean_1.2.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.2.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../08-ruby-minitest_5.10.3-1_all.deb ...
Unpacking ruby-minitest (5.10.3-1) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../09-ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../10-ruby-power-assert_0.3.0-1_all.deb ...
Unpacking ruby-power-assert (0.3.0-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../11-ruby-test-unit_3.2.5-1_all.deb ...
Unpacking ruby-test-unit (3.2.5-1) ...
Selecting previously unselected package libruby2.5:amd64.
Preparing to unpack .../12-libruby2.5_2.5.1-1ubuntu1.13_amd64.deb ...
Unpacking libruby2.5:amd64 (2.5.1-1ubuntu1.13) ...
Selecting previously unselected package unzip.
Preparing to unpack .../13-unzip_6.0-21ubuntu1.2_amd64.deb ...
Unpacking unzip (6.0-21ubuntu1.2) ...
Selecting previously unselected package zip.
Preparing to unpack .../14-zip_3.0-11build1_amd64.deb ...
Unpacking zip (3.0-11build1) ...
Setting up libjs-jquery (3.2.1-1) ...
Setting up unzip (6.0-21ubuntu1.2) ...
Setting up zip (3.0-11build1) ...
Setting up fonts-lato (2.0-2) ...
Setting up ruby-did-you-mean (1.2.0-2) ...
Setting up ruby-net-telnet (0.1.1-2) ...
Setting up rubygems-integration (1.11) ...
Setting up javascript-common (11) ...
Setting up ruby-minitest (5.10.3-1) ...
Setting up ruby-power-assert (0.3.0-1) ...
Setting up ruby2.5 (2.5.1-1ubuntu1.13) ...
Setting up ruby (1:2.5.1) ...
Setting up ruby-test-unit (3.2.5-1) ...
Setting up rake (12.3.1-1ubuntu0.1) ...
Setting up libruby2.5:amd64 (2.5.1-1ubuntu1.13) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.5) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb 
Traceback (most recent call last):
    2: from /usr/bin/redis-trib.rb:25:in `<main>'
    1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- redis (LoadError)

##使用 gem 工具安装 ruby 的redis模块
[root@Redis-Ubuntu1804-node1:~]# gem install redis
Fetching: redis-5.0.6.gem (100%)
Successfully installed redis-5.0.6
Parsing documentation for redis-5.0.6
Installing ri documentation for redis-5.0.6
Done installing documentation for redis after 0 seconds
1 gem installed

##离线模式安装 gem
[root@Redis-Ubuntu1804-node1:~]# wget https://rubygems.org/downloads/redis-4.0.3.gem
[root@Redis-Ubuntu1804-node1:~]# gem install redis-4.0.3.gem 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb
Usage: redis-trib <command> <options> <arguments ...>

  create          host1:port1 ... hostN:portN  #创建集群
                  --replicas <arg>  #指定每个master节点的副本数，即每组主从的slave节点数，通常为1
  check           host:port  #检查集群信息
  info            host:port  #查看集群主机信息
  fix             host:port  #修复集群
                  --timeout <arg>
  reshard         host:port  #在线热机迁移指定的slots数据
                  --from <arg>
                  --to <arg>
                  --slots <arg>
                  --yes
                  --timeout <arg>
                  --pipeline <arg>
  rebalance       host:port  #平衡集群在线节点的slots数量
                  --weight <arg>
                  --auto-weights
                  --use-empty-masters
                  --timeout <arg>
                  --simulate
                  --pipeline <arg>
                  --threshold <arg>
  add-node        new_host:new_port existing_host:existing_port  #添加新的节点到集群中
                  --slave
                  --master-id <arg>
  del-node        host:port node_id  #删除集群中的指定节点
  set-timeout     host:port milliseconds  #设置节点超时时间
  call            host:port command arg arg .. arg  #在集群上所有节点上执行命令
  import          host:port  #导入外部redis服务器数据到当前集群
                  --from <arg>
                  --copy
                  --replace
  help            (show this help)

For check, fix, reshard, del-node, set-timeout you can specify the host and port of any working node in the cluster.

[root@Redis-Ubuntu1804-node1:~]# sed -i 's/@r = Redis.new.*/@r = Redis.new(:host => @info[:host], :port => @info[:port], :timeout => 60, :password => "'redis'")/' /usr/bin/redis-trib.rb
[root@Redis-Ubuntu1804-node1:~]# vim /usr/bin/redis-trib.rb

 def connect(o={})
        return if @r
        print "Connecting to node #{self}: " if $verbose
        STDOUT.flush
        begin
            @r = Redis.new(:host => @info[:host], :port => @info[:port], :timeout => 60, :password => 'redis')                                  
            @r.ping
        rescue
            xputs "[ERR] Sorry, can't connect to node #{self}"
            exit 1 if o[:abort]
            @r = nil
        end
        xputs "OK" if $verbose
    end

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 0 slots | 0 slaves.
[OK] 0 keys in 1 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb create --replicas 1 10.0.0.20:6379 10.0.0.21:6379 10.0.0.22:6379 10.0.0.30:6379 10.0.0.31:6379 10.0.0.32:6379
>>> Creating cluster
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
10.0.0.20:6379
10.0.0.21:6379
10.0.0.22:6379
Adding replica 10.0.0.31:6379 to 10.0.0.20:6379
Adding replica 10.0.0.32:6379 to 10.0.0.21:6379
Adding replica 10.0.0.30:6379 to 10.0.0.22:6379
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join......
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

#在所有节点上手动清空数据，并重置集群设置
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 --no-auth-warning flushall
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 --no-auth-warning cluster reset

[root@Redis-Ubuntu1804-node1:~]# cat /etc/redis/redis.conf | grep cluster-conf
# cluster-config-file nodes-6379.conf
cluster-config-file nodes-6379.conf
[root@Redis-Ubuntu1804-node1:~]# find / -name nodes-6379.conf
/var/lib/redis/nodes-6379.conf
[root@Redis-Ubuntu1804-node1:~]# cat /var/lib/redis/nodes-6379.conf 
f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379@16379 slave 709b09b96f19209e7f0a1e3cfc5c035678491e4b 0 1681979886000 4 connected
1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379@16379 myself,master - 0 1681979886000 1 connected 0-5460
337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379@16379 master - 0 1681979888000 2 connected 5461-10922
c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379@16379 slave 1c2fee65ee50cdf66c862d04710672286b305f55 0 1681979888959 5 connected
709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379@16379 master - 0 1681979887000 3 connected 10923-16383
0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379@16379 slave 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 0 1681979888000 6 connected
vars currentEpoch 6 lastVoteEpoch 0
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 5462 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 5461 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.


[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:1000
cluster_stats_messages_pong_sent:1033
cluster_stats_messages_sent:2033
cluster_stats_messages_ping_received:1028
cluster_stats_messages_pong_received:1000
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:2033


[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 cluster nodes
f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379@16379 slave 709b09b96f19209e7f0a1e3cfc5c035678491e4b 0 1681980883096 4 connected
1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379@16379 myself,master - 0 1681980882000 1 connected 0-5460
337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379@16379 master - 0 1681980885110 2 connected 5461-10922
c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379@16379 slave 1c2fee65ee50cdf66c862d04710672286b305f55 0 1681980883000 5 connected
709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379@16379 master - 0 1681980884000 3 connected 10923-16383
0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379@16379 slave 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 0 1681980884103 6 connected

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 info replication
# Replication
role:master
connected_slaves:1
slave0:ip=10.0.0.31,port=6379,state=online,offset=1428,lag=1
master_replid:33b67c12391d0787c01305ee41ccba34db5c843b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:1428
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:1428

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.31 info replication
# Replication
role:slave
master_host:10.0.0.20
master_port:6379
master_link_status:up
master_last_io_seconds_ago:6
master_sync_in_progress:0
slave_repl_offset:1554
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:33b67c12391d0787c01305ee41ccba34db5c843b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:1554
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:1554

[root@Client-Ubuntu-1804-250:~/script/redis]# ./redis_cluster_newData.py 100

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 30 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 31 keys | 5462 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 39 keys | 5461 slots | 1 slaves.
[OK] 100 keys in 3 masters.
0.01 keys per slot on average.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 -c get keys11
"value11"
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 get keys11
"value11"
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.20 get keys12
(error) MOVED 14046 10.0.0.22:6379
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -p 6379 -h 10.0.0.22 get keys12
"value12"

[root@Redis-Ubuntu1804-node3:~]# systemctl stop redis
[root@Redis-Ubuntu1804-node3:~]# 
##初始信息
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
##故障发生第一时间
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
[ERR] Sorry, can't connect to node 10.0.0.22:6379
*** WARNING: 10.0.0.30:6379 claims to be slave of unknown node ID 709b09b96f19209e7f0a1e3cfc5c035678491e4b.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[ERR] Not all 16384 slots are covered by nodes.
##自动提升Msater
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
M: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots:10923-16383 (5461 slots) master
   0 additional replica(s)
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

1021:M 20 Apr 17:45:33.030 * Marking node 709b09b96f19209e7f0a1e3cfc5c035678491e4b as failing (quorum reached).
1021:M 20 Apr 17:45:33.030 # Cluster state changed: fail
1021:M 20 Apr 17:45:34.067 # Failover auth granted to f9e73307b3146b25b51cec9a861463a616ed322b for epoch 7
1021:M 20 Apr 17:45:34.070 # Cluster state changed: ok

[root@Redis-Ubuntu1804-node3:~]# systemctl start redis
[root@Redis-Ubuntu1804-node3:~]# 


[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
M: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
S: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots: (0 slots) slave
   replicates f9e73307b3146b25b51cec9a861463a616ed322b
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

1014:M 20 Apr 17:45:33.030 * Marking node 709b09b96f19209e7f0a1e3cfc5c035678491e4b as failing (quorum reached).
1014:M 20 Apr 17:45:33.030 # Cluster state changed: fail
1014:M 20 Apr 17:45:34.067 # Failover auth granted to f9e73307b3146b25b51cec9a861463a616ed322b for epoch 7
1014:M 20 Apr 17:45:34.070 # Cluster state changed: ok
1014:M 20 Apr 17:51:47.852 * Clear FAIL state for node 709b09b96f19209e7f0a1e3cfc5c035678491e4b: master without slots is reachable again.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 150 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 141 keys | 5462 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 154 keys | 5461 slots | 1 slaves.
[OK] 445 keys in 3 masters.
0.03 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster add-node 10.0.0.23:6379 10.0.0.20:6379
>>> Adding node 10.0.0.23:6379 to cluster 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 10.0.0.23:6379 to make it join the cluster.
[OK] New node added correctly.
[root@Redis-Ubuntu1804-node1:~]# 

##10.0.0.23 节点已经加入到集群中，但是未分配任何槽位数据，也没有从节点
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 150 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 141 keys | 5462 slots | 1 slaves.
10.0.0.23:6379 (ac947d4f...) -> 0 keys | 0 slots | 0 slaves.
10.0.0.30:6379 (5c9789e1...) -> 154 keys | 5461 slots | 1 slaves.
[OK] 445 keys in 4 masters.
0.03 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 150 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 141 keys | 5462 slots | 1 slaves.
10.0.0.23:6379 (ac947d4f...) -> 0 keys | 0 slots | 0 slaves.
10.0.0.30:6379 (5c9789e1...) -> 154 keys | 5461 slots | 1 slaves.
[OK] 445 keys in 4 masters.
0.03 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots: (0 slots) master
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.20 --no-auth-warning flushall
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.21 --no-auth-warning flushall
OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.30 --no-auth-warning flushall
OK

##为新节点分配槽位
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots: (0 slots) master
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 4096   ##需要进行重新分配的槽位数
What is the receiving node ID? ac947d4fc970b79c2364ce305441906b462f8b65  ##接收分配槽位的节点 node id
Please enter all the source node IDs.  ##提供重新分配槽位的节点node id
  Type 'all' to use all the nodes as source nodes for the hash slots. ##输入all将从拥有槽位的所有节点进行自动分配
  Type 'done' once you entered all the source nodes IDs. ##输入提供槽位的节点node id，输入done结束
Source node #1: all
...
...
...
    Moving slot 12280 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12281 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12282 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12283 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12284 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12285 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12286 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
    Moving slot 12287 from 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
Do you want to proceed with the proposed reshard plan (yes/no)? yes ##确认槽位分配方案
...
...
...
Moving slot 12280 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12281 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12282 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12283 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12284 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12285 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12286 from 10.0.0.30:6379 to 10.0.0.23:6379: 
Moving slot 12287 from 10.0.0.30:6379 to 10.0.0.23:6379:

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.23:6379 (ac947d4f...) -> 0 keys | 4096 slots | 0 slaves.
10.0.0.30:6379 (5c9789e1...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster add-node 10.0.0.33:6379 10.0.0.20:6379 --cluster-slave --cluster-master-id ac947d4fc970b79c2364ce305441906b462f8b65
>>> Adding node 10.0.0.33:6379 to cluster 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 10.0.0.33:6379 to make it join the cluster.
Waiting for the cluster to join

>>> Configure node as replica of 10.0.0.23:6379.
[OK] New node added correctly.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.23:6379 (ac947d4f...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: 829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379
   slots: (0 slots) slave
   replicates ac947d4fc970b79c2364ce305441906b462f8b65
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb add-node 10.0.0.23:6379 10.0.0.20:6379
>>> Adding node 10.0.0.23:6379 to cluster 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 10.0.0.23:6379 to make it join the cluster.
[OK] New node added correctly.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.23:6379 (0e504f59...) -> 0 keys | 0 slots | 0 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots: (0 slots) master
   0 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb call 10.0.0.20:6379 flushall
>>> Calling FLUSHALL
10.0.0.20:6379: OK
10.0.0.31:6379: READONLY You can't write against a read only slave.
10.0.0.22:6379: OK
10.0.0.32:6379: READONLY You can't write against a read only slave.
10.0.0.23:6379: OK
10.0.0.30:6379: READONLY You can't write against a read only slave.
10.0.0.21:6379: OK
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots: (0 slots) master
   0 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 4096
What is the receiving node ID? 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1:all
Do you want to proceed with the proposed reshard plan (yes/no)? yes
...
...
...
Moving slot 12281 from 10.0.0.22:6379 to 10.0.0.23:6379: 
Moving slot 12282 from 10.0.0.22:6379 to 10.0.0.23:6379: 
Moving slot 12283 from 10.0.0.22:6379 to 10.0.0.23:6379: 
Moving slot 12284 from 10.0.0.22:6379 to 10.0.0.23:6379: 
Moving slot 12285 from 10.0.0.22:6379 to 10.0.0.23:6379: 
Moving slot 12286 from 10.0.0.22:6379 to 10.0.0.23:6379: 
Moving slot 12287 from 10.0.0.22:6379 to 10.0.0.23:6379:

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.23:6379 (0e504f59...) -> 0 keys | 4096 slots | 0 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:0-1364,5461-6826,10923-12287 (4096 slots) master
   0 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb add-node --slave --master-id 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.33:6379 10.0.0.20:6379
>>> Adding node 10.0.0.33:6379 to cluster 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:0-1364,5461-6826,10923-12287 (4096 slots) master
   0 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 10.0.0.33:6379 to make it join the cluster.
Waiting for the cluster to join.
>>> Configure node as replica of 10.0.0.23:6379.
[OK] New node added correctly.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.23:6379 (0e504f59...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: 6e761ee02c9c17838e4643b9030ddfe327f1c742 10.0.0.33:6379
   slots: (0 slots) slave
   replicates 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:0-1364,5461-6826,10923-12287 (4096 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster check 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.23:6379 (ac947d4f...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: 829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379
   slots: (0 slots) slave
   replicates ac947d4fc970b79c2364ce305441906b462f8b65
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: 829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379
   slots: (0 slots) slave
   replicates ac947d4fc970b79c2364ce305441906b462f8b65
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 1365
What is the receiving node ID? 6b142fe3438c3ea488c34366e5ea5a298f89f518
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1: ac947d4fc970b79c2364ce305441906b462f8b65
Source node #2: done
Do you want to proceed with the proposed reshard plan (yes/no)? yes


[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379
   slots: (0 slots) slave
   replicates ac947d4fc970b79c2364ce305441906b462f8b65
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots:[5461-6826],[10923-12287] (2731 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 1366
What is the receiving node ID? a4b387d82ac06e5cbf212e48c781e1c27b50320f
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1: ac947d4fc970b79c2364ce305441906b462f8b65
Source node #2: done
Do you want to proceed with the proposed reshard plan (yes/no)? yes


[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379
   slots: (0 slots) slave
   replicates ac947d4fc970b79c2364ce305441906b462f8b65
S: 07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379
   slots: (0 slots) slave
   replicates 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
M: a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
M: ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379
   slots:[10923-12287] (1365 slots) master
   1 additional replica(s)
S: 6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379
   slots: (0 slots) slave
   replicates a4b387d82ac06e5cbf212e48c781e1c27b50320f
S: 60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 6b142fe3438c3ea488c34366e5ea5a298f89f518
M: 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 1365
What is the receiving node ID? 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1: ac947d4fc970b79c2364ce305441906b462f8b65
Source node #2: done
Do you want to proceed with the proposed reshard plan (yes/no)? yes

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 5462 slots | 1 slaves.
10.0.0.23:6379 (ac947d4f...) -> 0 keys | 0 slots | 0 slaves.
10.0.0.30:6379 (5c9789e1...) -> 0 keys | 5461 slots | 2 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]#

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning cluster nodes
829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379@16379 slave 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 0 1682007712000 15 connected
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 slave 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 0 1682007713000 15 connected
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1682007713079 14 connected 5461-10922
ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379@16379 master - 0 1682007710000 12 connected
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1682007711000 14 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1682007712000 13 connected
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 master - 0 1682007714086 15 connected 10923-16383
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 myself,master - 0 1682007709000 13 connected 0-5460
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster del-node 10.0.0.20:6379 ac947d4fc970b79c2364ce305441906b462f8b65
>>> Removing node ac947d4fc970b79c2364ce305441906b462f8b65 from cluster 10.0.0.20:6379
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster del-node 10.0.0.20:6379 829eef61e20def1a36e02a99f1650c9267be2108
>>> Removing node 829eef61e20def1a36e02a99f1650c9267be2108 from cluster 10.0.0.20:6379
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning cluster nodes
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 slave 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 0 1682008285000 15 connected
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1682008285000 14 connected 5461-10922
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1682008286181 14 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1682008283157 13 connected
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 master - 0 1682008285173 15 connected 10923-16383
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 myself,master - 0 1682008283000 13 connected 0-5460

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 0 keys | 5462 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 0 keys | 5461 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node4:~]# cat /app/redis/data/nodes-6379.conf 
6b142fe3438c3ea488c34366e5ea5a298f89f518 10.0.0.20:6379@16379 master - 0 1682007475000 13 connected 0-5460
6a9dd64b6bf1a7eb336ec9d320d86ae7450d5e2b 10.0.0.32:6379@16379 slave a4b387d82ac06e5cbf212e48c781e1c27b50320f 0 1682007476000 14 connected
829eef61e20def1a36e02a99f1650c9267be2108 10.0.0.33:6379@16379 slave 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 0 1682007474000 15 connected
ac947d4fc970b79c2364ce305441906b462f8b65 10.0.0.23:6379@16379 myself,master - 0 1682007470000 12 connected
a4b387d82ac06e5cbf212e48c781e1c27b50320f 10.0.0.21:6379@16379 master - 0 1682007475000 14 connected 5461-10922
5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 10.0.0.30:6379@16379 master - 0 1682007477017 15 connected 10923-16383
07a36af61eb1f887419f2266b2360b4f795bb7a3 10.0.0.22:6379@16379 slave 5c9789e105f8d8a0f1dc5ac2a6d51831482fbd34 0 1682007476000 15 connected
60aec73a6b0d3929cda3a284bb513898d2e73657 10.0.0.31:6379@16379 slave 6b142fe3438c3ea488c34366e5ea5a298f89f518 0 1682007476010 13 connected
vars currentEpoch 15 lastVoteEpoch 0
[root@Redis-Ubuntu1804-node4:~]# rm -rf /app/redis/data/nodes-6379.conf

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.23:6379 (0e504f59...) -> 0 keys | 4096 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: 6e761ee02c9c17838e4643b9030ddfe327f1c742 10.0.0.33:6379
   slots: (0 slots) slave
   replicates 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:0-1364,5461-6826,10923-12287 (4096 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: 6e761ee02c9c17838e4643b9030ddfe327f1c742 10.0.0.33:6379
   slots: (0 slots) slave
   replicates 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:0-1364,5461-6826,10923-12287 (4096 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 1365
What is the receiving node ID? 1c2fee65ee50cdf66c862d04710672286b305f55
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1:0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
Source node #2:done
Do you want to proceed with the proposed reshard plan (yes/no)? yes


[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: 6e761ee02c9c17838e4643b9030ddfe327f1c742 10.0.0.33:6379
   slots: (0 slots) slave
   replicates 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:5461-6826,10923-12287 (2731 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 1366
What is the receiving node ID? 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1:0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
Source node #2:done
Do you want to proceed with the proposed reshard plan (yes/no)? yes

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb reshard 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:12288-16383 (4096 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: 6e761ee02c9c17838e4643b9030ddfe327f1c742 10.0.0.33:6379
   slots: (0 slots) slave
   replicates 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots:10923-12287 (1365 slots) master
   1 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 1365
What is the receiving node ID? 709b09b96f19209e7f0a1e3cfc5c035678491e4b
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1:0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
Source node #2:done
Do you want to proceed with the proposed reshard plan (yes/no)? yes

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 5461 slots | 2 slaves.
10.0.0.23:6379 (0e504f59...) -> 0 keys | 0 slots | 0 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 4 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   2 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: 6e761ee02c9c17838e4643b9030ddfe327f1c742 10.0.0.33:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a 10.0.0.23:6379
   slots: (0 slots) master
   0 additional replica(s)
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb del-node 10.0.0.20:6379 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a
>>> Removing node 0e504f596a5e8b55d0a38f5eacd3bd4b5c8f462a from cluster 10.0.0.20:6379
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb del-node 10.0.0.20:6379 6e761ee02c9c17838e4643b9030ddfe327f1c742
>>> Removing node 6e761ee02c9c17838e4643b9030ddfe327f1c742 from cluster 10.0.0.20:6379
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb check 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning --cluster call 10.0.0.20:6379 config set requirepass ''
>>> Calling config set requirepass 
10.0.0.20:6379: OK
10.0.0.22:6379: OK
10.0.0.21:6379: OK
10.0.0.32:6379: OK
10.0.0.31:6379: OK
10.0.0.30:6379: OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.33 --no-auth-warning config set requirepass ''
OK

[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis --cluster info 10.0.0.20:6379
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
10.0.0.20:6379 (6b142fe3...) -> 1 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 1 keys | 5462 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 2 keys | 5461 slots | 1 slaves.
[OK] 4 keys in 3 masters.
0.00 keys per slot on average.

[root@Redis-Ubuntu1804-node1:~]# redis-cli --cluster import 10.0.0.20:6379 --cluster-from 10.0.0.33:6379 --cluster-copy --cluster-replace ... ... ... Migrating key_7867 to 10.0.0.20:6379: OK Migrating key_6810 to 10.0.0.20:6379: OK Migrating key_1232 to 10.0.0.21:6379: OK Migrating key_10171 to 10.0.0.21:6379: OK Migrating key_15561 to 10.0.0.30:6379: OK Migrating key_13723 to 10.0.0.21:6379: OK Migrating key_18761 to 10.0.0.21:6379: OK Migrating key_14471 to 10.0.0.20:6379: OK Migrating key_12496 to 10.0.0.30:6379: OK Migrating key_10559 to 10.0.0.21:6379: OK Migrating key_15282 to 10.0.0.21:6379: OK Migrating key_19021 to 10.0.0.21:6379: OK Migrating key_12831 to 10.0.0.21:6379: OK Migrating key_13260 to 10.0.0.20:6379: OK Migrating key_15767 to 10.0.0.30:6379: OK

[root@Redis-Ubuntu1804-node1:~]# redis-cli --cluster info 10.0.0.20:6379
10.0.0.20:6379 (6b142fe3...) -> 6662 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (a4b387d8...) -> 6666 keys | 5462 slots | 1 slaves.
10.0.0.30:6379 (5c9789e1...) -> 6676 keys | 5461 slots | 1 slaves.
[OK] 20004 keys in 3 masters.
1.22 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -c --no-auth-warning get key_2981
"value-2981"
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb call 10.0.0.20:6379 config set requirepass ''
>>> Calling CONFIG set requirepass 
10.0.0.20:6379: OK
10.0.0.31:6379: OK
10.0.0.22:6379: OK
10.0.0.32:6379: OK
10.0.0.30:6379: OK
10.0.0.21:6379: OK
[root@Redis-Ubuntu1804-node1:~]# redis-cli -a redis -h 10.0.0.33 config set requirepass ''
OK
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
[ERR] Sorry, can't connect to node 10.0.0.20:6379

##清理 redis-trib.rb 工具配置的密码
[root@Redis-Ubuntu1804-node1:~]# sed -i 's/@r = Redis.new.*/@r = Redis.new(:host => @info[:host], :port => @info[:port], :timeout => 60)/' /usr/bin/redis-trib.rb
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 0 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb import --from 10.0.0.33:6379 --copy --replace 10.0.0.20:6379
>>> Importing data from 10.0.0.33:6379 to cluster 
>>> Performing Cluster Check (using node 10.0.0.20:6379)
M: 1c2fee65ee50cdf66c862d04710672286b305f55 10.0.0.20:6379
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: c567eea1d3fda7b37c42b741bc32d14385bbe872 10.0.0.31:6379
   slots: (0 slots) slave
   replicates 1c2fee65ee50cdf66c862d04710672286b305f55
M: 709b09b96f19209e7f0a1e3cfc5c035678491e4b 10.0.0.22:6379
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 0428f9a71c369004c0ca01c0a403f9c2ee5fa41c 10.0.0.32:6379
   slots: (0 slots) slave
   replicates 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e
S: f9e73307b3146b25b51cec9a861463a616ed322b 10.0.0.30:6379
   slots: (0 slots) slave
   replicates 709b09b96f19209e7f0a1e3cfc5c035678491e4b
M: 337bf2a15dd9b0ae8caaee08c5ec41beb754b78e 10.0.0.21:6379
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Connecting to the source Redis instance
*** Importing 20000 keys from DB 0
Traceback (most recent call last):
    11: from /usr/bin/redis-trib.rb:1830:in `<main>'
    10: from /usr/bin/redis-trib.rb:1604:in `import_cluster_cmd'
     9: from /var/lib/gems/2.5.0/gems/redis-5.0.6/lib/redis/commands/keys.rb:26:in `scan'
     8: from /var/lib/gems/2.5.0/gems/redis-5.0.6/lib/redis/commands/keys.rb:433:in `_scan'
     7: from /var/lib/gems/2.5.0/gems/redis-5.0.6/lib/redis.rb:166:in `send_command'
     6: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
     5: from /var/lib/gems/2.5.0/gems/redis-5.0.6/lib/redis.rb:167:in `block in send_command'
     4: from /var/lib/gems/2.5.0/gems/redis-5.0.6/lib/redis/client.rb:73:in `call_v'
     3: from /var/lib/gems/2.5.0/gems/redis-client-0.14.1/lib/redis_client.rb:223:in `call_v'
     2: from /var/lib/gems/2.5.0/gems/redis-client-0.14.1/lib/redis_client/command_builder.rb:68:in `generate'
     1: from /var/lib/gems/2.5.0/gems/redis-client-0.14.1/lib/redis_client/command_builder.rb:68:in `map!'
/var/lib/gems/2.5.0/gems/redis-client-0.14.1/lib/redis_client/command_builder.rb:75:in `block in generate': Unsupported command argument type: NilClass (TypeError)

[root@Redis-Ubuntu1804-node1:~]# gem uninstall redis
Successfully uninstalled redis-5.0.6
[root@Redis-Ubuntu1804-node1:~]# wget https://rubygems.org/downloads/redis-4.0.3.gem
--2023-04-21 03:36:14--  https://rubygems.org/downloads/redis-4.0.3.gem
Resolving rubygems.org (rubygems.org)... 151.101.1.227, 151.101.65.227, 151.101.129.227, ...
Connecting to rubygems.org (rubygems.org)|151.101.1.227|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 116224 (114K) [application/octet-stream]
Saving to: ‘redis-4.0.3.gem’

redis-4.0.3.gem                     100%[===================================================================>] 113.50K  --.-KB/s    in 0.1s    

2023-04-21 03:36:14 (1.11 MB/s) - ‘redis-4.0.3.gem’ saved [116224/116224]

[root@Redis-Ubuntu1804-node1:~]# gem install redis-4.0.3.gem 
Successfully installed redis-4.0.3
Parsing documentation for redis-4.0.3
Installing ri documentation for redis-4.0.3
Done installing documentation for redis after 0 seconds
1 gem installed
[root@Redis-Ubuntu1804-node1:~]# 

Migrating key_2307 to 10.0.0.22:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_5080 to 10.0.0.20:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_15899 to 10.0.0.21:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_6538 to 10.0.0.22:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_1665 to 10.0.0.20:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_14837 to 10.0.0.21:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_1757 to 10.0.0.20:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
Migrating key_13190 to 10.0.0.20:6379: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)

[root@Redis-Ubuntu1804-node1:~]# gem uninstall redis
Successfully uninstalled redis-4.0.3
[root@Redis-Ubuntu1804-node1:~]# wget https://rubygems.org/downloads/redis-3.3.5.gem
--2023-04-21 03:46:33--  https://rubygems.org/downloads/redis-3.3.5.gem
Resolving rubygems.org (rubygems.org)... 151.101.193.227, 151.101.129.227, 151.101.65.227, ...
Connecting to rubygems.org (rubygems.org)|151.101.193.227|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 92672 (90K) [application/octet-stream]
Saving to: ‘redis-3.3.5.gem’

redis-3.3.5.gem                     100%[===================================================================>]  90.50K   497KB/s    in 0.2s    

2023-04-21 03:46:34 (497 KB/s) - ‘redis-3.3.5.gem’ saved [92672/92672]

[root@Redis-Ubuntu1804-node1:~]# gem install redis-3.3.5.gem 
Successfully installed redis-3.3.5
Parsing documentation for redis-3.3.5
Installing ri documentation for redis-3.3.5
Done installing documentation for redis after 0 seconds
1 gem installed

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb import --from 10.0.0.33:6379 --copy --replace 10.0.0.20:6379
...
...
...
Migrating key_19321 to 10.0.0.20:6379: OK
Migrating key_3394 to 10.0.0.20:6379: OK
Migrating key_11273 to 10.0.0.22:6379: OK
Migrating key_15899 to 10.0.0.21:6379: OK
Migrating key_14837 to 10.0.0.21:6379: OK
Migrating key_1665 to 10.0.0.20:6379: OK
Migrating key_5080 to 10.0.0.20:6379: OK
Migrating key_13190 to 10.0.0.20:6379: OK
Migrating key_1757 to 10.0.0.20:6379: OK
Migrating key_6538 to 10.0.0.22:6379: OK
Migrating key_2307 to 10.0.0.22:6379: OK
[root@Redis-Ubuntu1804-node1:~]# 

[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb info 10.0.0.20:6379
10.0.0.20:6379 (1c2fee65...) -> 6661 keys | 5461 slots | 1 slaves.
10.0.0.22:6379 (709b09b9...) -> 6674 keys | 5461 slots | 1 slaves.
10.0.0.21:6379 (337bf2a1...) -> 6665 keys | 5462 slots | 1 slaves.
[OK] 20000 keys in 3 masters.
1.22 keys per slot on average.
[root@Redis-Ubuntu1804-node1:~]# redis-cli -c get key_12332
"value-12332"
[root@Redis-Ubuntu1804-node1:~]# 

#查看指定槽位中的键值数
[root@Redis-Ubuntu1804-node1:~]# redis-cli cluster countkeysinslot 0
(integer) 3
[root@Redis-Ubuntu1804-node1:~]# redis-cli cluster countkeysinslot 16383
(integer) 0
[root@Redis-Ubuntu1804-node1:~]# redis-cli cluster countkeysinslot 1
(integer) 2
[root@Redis-Ubuntu1804-node1:~]# 

#槽位自动平衡分布
[root@Redis-Ubuntu1804-node1:~]# redis-trib.rb rebalance 10.0.0.20:6379
>>> Performing Cluster Check (using node 10.0.0.20:6379)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
*** No rebalancing needed! All nodes are within the 2.0% threshold.
[root@Redis-Ubuntu1804-node1:~]# 

#查找bigkeys,建议在slave上执行
[root@Redis-Ubuntu1804-node1:~]# redis-cli --bigkeys

# Scanning the entire keyspace to find biggest keys as well as
# average sizes per key type.  You can use -i 0.1 to sleep 0.1 sec
# per 100 SCAN commands (not usually needed).

[00.00%] Biggest string found so far 'key_13312' with 11 bytes

-------- summary -------

Sampled 6661 keys in the keyspace!
Total key length in bytes is 56245 (avg len 8.44)

Biggest string found 'key_13312' has 11 bytes

6661 strings with 69567 bytes (100.00% of keys, avg size 10.44)
0 lists with 0 items (00.00% of keys, avg size 0.00)
0 sets with 0 members (00.00% of keys, avg size 0.00)
0 hashs with 0 fields (00.00% of keys, avg size 0.00)
0 zsets with 0 members (00.00% of keys, avg size 0.00)
0 streams with 0 entries (00.00% of keys, avg size 0.00)
[root@Redis-Ubuntu1804-node1:~]# 

[root@Client-Ubuntu-1804-250:~/script/redis]# cat redis_install.sh 
#!/bin/bash
#
#********************************************************************
#Author:                janzen
#Date:                  2023-04-13
#FileName：             redis_install.sh
#Description：          Install Redis
#Copyright (C):        2023 All rights reserved
#********************************************************************

DIR='/app/redis'
DIR_S='\/app\/redis'
PASSWD='redis'
PORT=()
echo -e "启用架构：\n 1、single node \n 2、Replicae_node \n 3、Cluster_node\n"
read -p "选择节点类型：" node_type
read -p "创建的副本数：" num
case $num in
        0)
                echo 不可创建0副本
                exit
        ;;
        [1-9]*)
                echo 创建$num副本
        ;;
        *)
                echo $num 不是数字
                exit
        ;;
esac
for i in $(seq $num); do
        rds_port=`echo $i-1+6379|bc`
        PORT+=($rds_port)
done

wget https://download.redis.io/releases/redis-5.0.14.tar.gz
tar xf redis-5.0.14.tar.gz
useradd redis -s /sbin/nologin
mkdir $DIR/{etc,log,data,run} -p
chown redis.redis $DIR/ -R
apt-get install build-essential tree -y
cd redis-5.0.14
make PREFIX=$DIR install
ln -s $DIR/bin/* /usr/bin/


echo net.core.somaxconn=1024 >> /etc/sysctl.conf
echo vm.overcommit_memory=1 >> /etc/sysctl.conf
sysctl -p
echo never > /sys/kernel/mm/transparent_hugepage/enabled
for i in ${PORT[*]};do
    case $node_type in
        1)
            sed -e 's/^bind 127.0.0.1/bind 0.0.0.0/' -e 's/^port 6379/port '"$i"'/' -e 's/^pidfile \/var\/run\/redis_6379.pid/pidfile '"$DIR_S"'\/run\/redis_'"$i"'.pid/' -e 's/^logfile ""/logfile "'"$DIR_S"'\/log\/redis_'"$i"'.log"/g' -e 's/^always-show-logo yes/always-show-logo no/g' -e 's/^appendonly no/appendonly yes/' -e 's/^appendfilename "appendonly.aof"/appendfilename "appendonly_'"$i"'.aof"/g' -e 's/^dbfilename dump.rdb/dbfilename dump_'"$i"'.rdb/g' -e 's/^dir \.\//dir '"$DIR_S"'\/data/g' -e 's/^# masterauth <master-password>$/masterauth '"$PASSWD"'/' -e 's/^# requirepass foobared/requirepass '"$PASSWD"'/' redis.conf > $DIR/etc/redis_$i.conf
            ;;
        2)
            read -p "node $i Master：<IP> <port>: " Master
            sed -e 's/^bind 127.0.0.1/bind 0.0.0.0/' -e 's/^port 6379/port '"$i"'/' -e 's/^pidfile \/var\/run\/redis_6379.pid/pidfile '"$DIR_S"'\/run\/redis_'"$i"'.pid/' -e 's/^logfile ""/logfile "'"$DIR_S"'\/log\/redis_'"$i"'.log"/g' -e 's/^always-show-logo yes/always-show-logo no/g' -e 's/^appendonly no/appendonly yes/' -e 's/^appendfilename "appendonly.aof"/appendfilename "appendonly_'"$i"'.aof"/g' -e 's/^dbfilename dump.rdb/dbfilename dump_'"$i"'.rdb/g' -e 's/^dir \.\//dir '"$DIR_S"'\/data/g' -e 's/^# masterauth <master-password>$/masterauth '"$PASSWD"'/' -e 's/^# requirepass foobared/requirepass '"$PASSWD"'/' -e '/# replicaof/a replicaof '"$Master"'' redis.conf > $DIR/etc/redis_$i.conf
            ;;
        3)
            sed -e 's/^bind 127.0.0.1/bind 0.0.0.0/' -e 's/^port 6379/port '"$i"'/' -e 's/^pidfile \/var\/run\/redis_6379.pid/pidfile '"$DIR_S"'\/run\/redis_'"$i"'.pid/' -e 's/^logfile ""/logfile "'"$DIR_S"'\/log\/redis_'"$i"'.log"/g' -e 's/^always-show-logo yes/always-show-logo no/g' -e 's/^appendonly no/appendonly yes/' -e 's/^appendfilename "appendonly.aof"/appendfilename "appendonly_'"$i"'.aof"/g' -e 's/^dbfilename dump.rdb/dbfilename dump_'"$i"'.rdb/g' -e 's/^dir \.\//dir '"$DIR_S"'\/data/g' -e 's/^# masterauth <master-password>$/masterauth '"$PASSWD"'/' -e 's/^# requirepass foobared/requirepass '"$PASSWD"'/' -e '/# cluster-enabled yes/a cluster-enabled yes' -e '/# cluster-config-file/a cluster-config-file nodes-'"$i"'.conf' -e '/# cluster-require-full-coverage yes/a cluster-require-full-coverage yes' redis.conf > $DIR/etc/redis_$i.conf
            ;;
        *)
            exit
            ;;
    esac
    cat > /etc/systemd/system/redis_$i.service << EOF
[Unit]
Description=Redis persistent key-value database
After=network.target
[Service]
ExecStart=$DIR/bin/redis-server $DIR/etc/redis_$i.conf --supervised systemd
ExecStop=/bin/kill -s QUIT $MAINPID
Type=notify
User=redis
Group=redis
RuntimeDirectory=redis
RuntimeDirectoryMode=0755
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
EOF
    chown redis.redis $DIR/ -R
    systemctl daemon-reload
    systemctl enable --now redis_$i.service
    redis-cli -a $PASSWD -P $I --no-auth-warning info keyspace
done

cat > /etc/init.d/disable_transparent_hugepage << EOF
#!/bin/bash
echo never > /sys/kernel/mm/transparent_hugepage/enabled
EOF
chmod 755 /etc/init.d/disable_transparent_hugepage
cd /etc/rcS.d/
ln -s ../init.d/disable_transparent_hugepage disable_transparent_hugepage

ss -ntl
ps -ef | grep redis-server
# reboot

#!/bin/bash
#
#********************************************************************
#Author:                janzen
#Date:                  2023-04-20
#FileName：             redis_install_apt.sh
#Description：          The test script
#Copyright (C):        2023 All rights reserved
#********************************************************************
apt install redis -y
sed -i.bak -e 's/bind 127.0.0.1/bind 0.0.0.0/' -e '/masterauth/a masterauth redis' -e '/# requirepass/a requirepass redis' -e '/# cluster-enabled yes/a cluster-enabled yes' -e '/# cluster-config-file/a cluster-config-file nodes-6379.conf' -e '/# cluster-require-full-coverage yes/a cluster-require-full-coverage yes' /etc/redis/redis.conf
systemctl restart redis
ss -ntl

[root@Client-Ubuntu-1804-250:~/script/redis]# cat add_slots.sh 
#!/bin/bash
#
#********************************************************************
#Author:                janzen
#Date:                  2023-04-20
#FileName：             add_slots.sh
#Description：          The test script
#Copyright (C):        2023 All rights reserved
#********************************************************************
host=$1
port=$2
start=$3
end=$4
passwd=redis

for slot in `seq $start $end`; do
    redis-cli -h $host -p $port -a $passwd --no-auth-warning cluster addslots $slot &&
    echo $slot add to node $host:$port
done

[root@Client-Ubuntu-1804-250:~/script/redis]# pip3 install redis-py-cluster
Collecting redis-py-cluster
  Downloading https://files.pythonhosted.org/packages/b2/96/153bbcf5dee29b52b2674e77a87ce864d381f72151737317529b7de4f337/redis_py_cluster-2.1.3-py2.py3-none-any.whl (42kB)
    100% |████████████████████████████████| 51kB 403kB/s 
Collecting redis<4.0.0,>=3.0.0 (from redis-py-cluster)
  Downloading https://files.pythonhosted.org/packages/a7/7c/24fb0511df653cf1a5d938d8f5d19802a88cef255706fdda242ff97e91b7/redis-3.5.3-py2.py3-none-any.whl (72kB)
    100% |████████████████████████████████| 81kB 1.5MB/s 
Installing collected packages: redis, redis-py-cluster
  Found existing installation: redis 2.10.6
    Not uninstalling redis at /usr/lib/python3/dist-packages, outside environment /usr
Successfully installed redis-3.5.3 redis-py-cluster-2.1.3

#!/usr/bin/python3
# -*- coding: UTF-8 -*-
#********************************************************************
#Author:                janzen
#Date:                  2023-04-20
#FileName：             redis_cluster_newData.py
#Description：          The python3 script
#Copyright (C):        2023 All rights reserved
#********************************************************************
from rediscluster import RedisCluster
import sys
num=int(sys.argv[1])

passwd='redis'

startup_nodes = [
    {"host":"10.0.0.20","port":"6379"},
    {"host":"10.0.0.21","port":"6379"},
    {"host":"10.0.0.22","port":"6379"},
    {"host":"10.0.0.30","port":"6379"},
    {"host":"10.0.0.31","port":"6379"},
    {"host":"10.0.0.32","port":"6379"}
    ]

redis_conn = RedisCluster(startup_nodes = startup_nodes,password = passwd,decode_responses=True)

for i in range(0,num):
    redis_conn.set("keys%s" % i,"value%s" % i)
    print("keys%s:" % i,redis_conn.get("keys%s" % i))

#!/usr/bin/python3
# -*- coding: UTF-8 -*-
#********************************************************************
#Author:                janzen
#Date:                  2023-04-20
#FileName：             redis_cluster_newData.py
#Description：          The python3 script
#Copyright (C):        2023 All rights reserved
#********************************************************************
from rediscluster import RedisCluster
import sys
num=int(sys.argv[1])

passwd='redis'

startup_nodes = [
    {"host":"10.0.0.20","port":"6379"},
    {"host":"10.0.0.21","port":"6379"},
    {"host":"10.0.0.22","port":"6379"},
    {"host":"10.0.0.30","port":"6379"},
    {"host":"10.0.0.31","port":"6379"},
    {"host":"10.0.0.32","port":"6379"}
    ]

redis_conn = RedisCluster(startup_nodes = startup_nodes,password = passwd,decode_responses=True)


while 1:
        time.sleep(1)
        try:
        redis_conn.set("keys%s" % num,"value%s" % num)
        print("set data %s:%s" % (num,redis_conn.get("keys%s" % num)))
        except Exception as err:
                print(err)
                continue
        num+=1

#!/usr/bin/python3
# -*- coding: UTF-8 -*-
#********************************************************************
#Author:                janzen
#Date:                  2023-04-20
#FileName：             redis_cluster_newData.py
#Description：          The python3 script
#Copyright (C):        2023 All rights reserved
#********************************************************************
from rediscluster import RedisCluster
import sys,time
num=int(sys.argv[1])

passwd='redis'

startup_nodes = [
    {"host":"10.0.0.20","port":"6379"},
    {"host":"10.0.0.21","port":"6379"},
    {"host":"10.0.0.22","port":"6379"},
    {"host":"10.0.0.30","port":"6379"},
    {"host":"10.0.0.31","port":"6379"},
    {"host":"10.0.0.32","port":"6379"}
    ]

redis_conn = RedisCluster(startup_nodes = startup_nodes,password = passwd,decode_responses=True)

while 1:
    time.sleep(1)
    try:
        print("get data %s:%s" % (str(num),redis_conn.get("keys"+str(num))))
    except Exception as err:
        print(err)
        continue