到了弃用Redis-sentinel架构的时候了

Posted 云原生生态圈

tags:

篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了到了弃用Redis-sentinel架构的时候了相关的知识，希望对你有一定的参考价值。

redis5.0新特性

  1. 新的流数据类型(Stream data type)

  2. 新的 Redis 模块 API：定时器、集群和字典 API(Timers, Cluster and Dictionary APIs)

  3. RDB 增加 LFU 和 LRU 信息

  4. 从 Ruby (redis-trib.rb)中将集群管理的C语言代码移植到了redis-cli 中

  5. 新的有序集合(sorted set)命令：ZPOPMIN/MAX 和阻塞变体(blocking variants)

  6. 升级 Active defragmentation 至 v2 版本

  7. 增强 HyperLogLog 的实现更好的内存统计报告许多包含子命令的命令现在都有一个 HELP 子命令

  8. 客户端频繁连接和断开连接时，性能表现更好许多

  9. 错误修复和其他方面的改进升级

  10. Jemalloc 至 5.1 版本

  11. 引入 CLIENT UNBLOCK 和 CLIENT ID

  12. 新增 LOLWUT 命令 antirez.com/news/123

  13. 在不存在需要保持向后兼容性的地方，弃用 "slave" 术语

  14. 网络层中的差异优化

  15. Lua 相关的改进

  16. 引入动态的 HZ(Dynamic HZ) 以平衡空闲 CPU 使用率和响应性

  17. 对 Redis 核心代码进行了重构并在许多方面进行了改进

服务的可用性

  1. 在集群分片的过程中，依旧可以提供部分的可用性，当集群一部分节点故障或者无法与其他节点通信,集群依旧可以运行

  2. 当集群中大部分主节点出现问题,集群将不可用

  3. 因为将哈希槽从一个节点移动到另一个节点不需要停止操作，所以添加和删除节点或更改节点持有的哈希槽的百分比都不需要停机

  4. redis cluster可以通过增加N个redis slave提高集群的可用性以及健壮性

Redis集群中节点端口

  1. 服务客户端常规tcp端口6379

  2. 大端口,为tcp端口加上10000,是一个数据端口，作为集群总线，主要用于节点与节点之间通信通道的二进制协议，它的功用还有:故障检测，配置更新，故障转移授权

Redis集群与Docker

当前的Redis集群不支持NAT网络模式以及被重新映射的IP和端口。如果使用docker部署redis,要使用 --network=host

Redis-cluster 5.0 部署篇

编译安装Redis二进制文件

 
   
   
 
    
  
    
    
  
  1. mkdir redisworkdir && cd $_
    2. 
  
    
    
  
  2. wget http://download.redis.io/releases/redis-5.0.8.tar.gz
    3. 
  
    
    
  
  3. tar xf redis-5.0.8.tar.gz
    4. 
  
    
    
  
  4. cd redis-5.0.8 && make # [option]此步之后可以选择make test.比较耗时,测试成功后会遇到以下信息。
    5. 
  
    
    
  
  5. #######
    6. 
  
    
    
  
  6. # 124 seconds - integration/replication-psync
    7. 
  
    
    
  
  7. # 108 seconds - unit/obuf-limits
    8. 
  
    
    
  
  8. # 98 seconds - unit/memefficiency
    9. 
  
    
    
  
  9. # 162 seconds - integration/replication
    10. 
  
    
    
  
  10. #
    11. 
  
    
    
  
  11. #\o/ All tests passed without errors!
    12. 
  
    
    
  
  12. #
    13. 
  
    
    
  
  13. #Cleanup: may take some time... OK
    14. 
  
    
    
  
  14. #make[1]: Leaving directory `/root/redis-5.0.8/src'
    15. 
  
    
    
  
  15. cp src/redis-cli src/redis-server /usr/local/bin/
    16.
准备Redis实例的基础配置文件
 
   
   
 
    
  
    
    
  
  1. cat << EOF > redis-7000.conf
    2. 
  
    
    
  
  2. port 7000
    3. 
  
    
    
  
  3. daemonize yes
    4. 
  
    
    
  
  4. dir "/data/redis/data"
    5. 
  
    
    
  
  5. dbfilename "dump-7000.rdb"
    6. 
  
    
    
  
  6. logfile "redis-7000.log"
    7. 
  
    
    
  
  7. cluster-enabled yes
    8. 
  
    
    
  
  8. cluster-config-file nodes-7000.conf
    9. 
  
    
    
  
  9. EOF
    10.
生成多实例配置文件

我们使用Redis Cluster方案，建议需要准备最少6个实例.

 
   
   
 
    
  
    
    
  
  1. redis-server redis-7000.conf
    2. 
  
    
    
  
  2. for i in `seq 7001 7005`
    3. 
  
    
    
  
  3. do
    4. 
  
    
    
  
  4.  sed "s/7000/$i/g" redis-7000.conf > redis-"$i".conf
    5. 
  
    
    
  
  5.  redis-server redis-"$i".conf
    6. 
  
    
    
  
  6. done
    7. 
  
    
    
  

    8. 
  
    
    
  
  8. [root@qiniu redis-5.0.8]# ps -ef |grep redis-server
    9. 
  
    
    
  

    10. 
  
    
    
  
  10. root 32284 1 0 21:24 ? 00:00:00 redis-server *:7000 [cluster]
    11. 
  
    
    
  
  11. root 32291 1 0 21:24 ? 00:00:00 redis-server *:7001 [cluster]
    12. 
  
    
    
  
  12. root 32297 1 0 21:24 ? 00:00:00 redis-server *:7002 [cluster]
    13. 
  
    
    
  
  13. root 32303 1 0 21:24 ? 00:00:00 redis-server *:7003 [cluster]
    14. 
  
    
    
  
  14. root 32309 1 0 21:24 ? 00:00:00 redis-server *:7004 [cluster]
    15. 
  
    
    
  
  15. root 32312 1 0 21:24 ? 00:00:00 redis-server *:7005 [cluster]
    16.

此时进去某一个Redis节点中会发现集群下线不可用的状态

 
   
   
 
    
  
    
    
  
  1. [root@qiniu redis-5.0.8]# redis-cli -p 7000
    2. 
  
    
    
  
  2. 127.0.0.1:7000> set hello world
    3. 
  
    
    
  
  3. (error) CLUSTERDOWN Hash slot not served
    4. 
  
    
    
  
  4. 127.0.0.1:7000> cluster info
    5. 
  
    
    
  
  5. cluster_state:fail
    6. 
  
    
    
  
  6. cluster_slots_assigned:0
    7. 
  
    
    
  
  7. cluster_slots_ok:0
    8. 
  
    
    
  
  8. cluster_slots_pfail:0
    9. 
  
    
    
  
  9. cluster_slots_fail:0
    10. 
  
    
    
  
  10. cluster_known_nodes:1
    11. 
  
    
    
  
  11. cluster_size:0
    12. 
  
    
    
  
  12. cluster_current_epoch:0
    13. 
  
    
    
  
  13. cluster_my_epoch:0
    14. 
  
    
    
  
  14. cluster_stats_messages_sent:0
    15. 
  
    
    
  
  15. cluster_stats_messages_received:0
    16. 
  
    
    
  
  16. 127.0.0.1:7000> cluster nodes
    17. 
  
    
    
  
  17. b1019e6e716125f14def5f35fac2c7024324a8ec :7000@17000 myself,master - 0 0 0 connected
    18.

Cluster节点主要的配置

 
   
   
 
    
  
    
    
  
  1. cluster-enabled yes
    2. 
  
    
    
  
  2. cluster-node-timeout 15000
    3. 
  
    
    
  
  3. cluster-config-file "nodes.conf"
    4. 
  
    
    
  
  4. clutser-require-full-coverage yes # 当集群中出现一个节点不合理,是否就标识集群不可用,一般配置为no
    5.
meet集群节点
 
   
   
 
    
  
    
    
  
  1. for i in `seq 7001 7005`
    2. 
  
    
    
  
  2. do
    3. 
  
    
    
  
  3.  redis-cli -h 127.0.0.1 -p 7000 cluster meet 127.0.0.1 "$i"
    4. 
  
    
    
  
  4. done
    5.

当连接到7002端口时候，就会发现redis-7002发现了7000和7001

 
   
   
 
    
  
    
    
  
  1. redis-cli -h 127.0.0.1 -p 7002 cluster nodes #这里会有6个节点
    2. 
  
    
    
  
  2. redis-cli -h 127.0.0.1 -p 7005 cluster info # 这里的cluster_know_nodes:6
    3.
分配槽位
 
   
   
 
    
  
    
    
  
  1. #!/bin/sbash
    2. 
  
    
    
  
  2. start=$1
    3. 
  
    
    
  
  3. end=$2
    4. 
  
    
    
  
  4. port=$3
    5. 
  
    
    
  
  5. for slot in `seq ${start} ${end}`
    6. 
  
    
    
  
  6. do
    7. 
  
    
    
  
  7.  echo "slot:${slot}"
    8. 
  
    
    
  
  8.  redis-cli -p ${port} cluster addslots ${slot}
    9. 
  
    
    
  
  9. done
    10. 
 
   
   
 
 
   
   
 
    
  
    
    
  
  1. chmod +x addslots.sh
    2. 
  
    
    
  
  2. ./addslots.sh 0 5460 7000
    3. 
  
    
    
  
  3. ./addslots.sh 5461 10922 7001
    4. 
  
    
    
  
  4. ./addslots.sh 10923 16383 7002
    5. 
  
    
    
  

    6. 
  
    
    
  
  6. ...
    7.
通过NodeID设置主从关系
 
   
   
 
    
  
    
    
  
  1. [root@qiniu redis-5.0.8]# redis-cli -h 127.0.0.1 -p 7000 cluster nodes
    2. 
  
    
    
  
  2. c28ad47247c7172faeddeebbfbbbcb7bf9f151b0 127.0.0.1:7002@17002 master - 0 1585835343000 4 connected 10923-16383
    3. 
  
    
    
  
  3. 5260ee3591f0a43698d71735dd57a65efb16dd2f 127.0.0.1:7004@17004 master - 0 1585835342000 3 connected
    4. 
  
    
    
  
  4. f68ef79fbed0b2faa59227037f99d09ac32295dc 127.0.0.1:7005@17005 master - 0 1585835342615 5 connected
    5. 
  
    
    
  
  5. df55c705abff3cc905eefadbc5332a9a59af9597 127.0.0.1:7003@17003 master - 0 1585835343617 2 connected
    6. 
  
    
    
  
  6. fb1026c49a5cccd2d18310a5bafd67433538bc78 127.0.0.1:7001@17001 master - 0 1585835341000 1 connected 5461-10922
    7. 
  
    
    
  
  7. fdd63d2dddddbca505b824685f7a03e08d88558b 127.0.0.1:7000@17000 myself,master - 0 1585835342000 0 connected 0-5460
    8. 
  
    
    
  
  8. redis-cli -h 127.0.0.1 -p 7003 cluster replicate fdd63d2dddddbca505b824685f7a03e08d88558b
    9. 
  
    
    
  
  9. redis-cli -h 127.0.0.1 -p 7004 cluster replicate fb1026c49a5cccd2d18310a5bafd67433538bc78
    10. 
  
    
    
  
  10. redis-cli -h 127.0.0.1 -p 7005 cluster replicate c28ad47247c7172faeddeebbfbbbcb7bf9f151b0
    11. 
  
    
    
  

    12. 
  
    
    
  
  12. [root@qiniu redis-5.0.8]# redis-cli -h 127.0.0.1 -p 7000 cluster info
    13. 
  
    
    
  
  13. cluster_state:ok
    14. 
  
    
    
  
  14. cluster_slots_assigned:16384
    15. 
  
    
    
  
  15. cluster_slots_ok:16384
    16. 
  
    
    
  
  16. cluster_slots_pfail:0
    17. 
  
    
    
  
  17. cluster_slots_fail:0
    18. 
  
    
    
  
  18. cluster_known_nodes:6
    19. 
  
    
    
  
  19. cluster_size:3
    20. 
  
    
    
  
  20. cluster_current_epoch:5
    21. 
  
    
    
  
  21. cluster_my_epoch:0
    22. 
  
    
    
  
  22. cluster_stats_messages_ping_sent:577
    23. 
  
    
    
  
  23. cluster_stats_messages_pong_sent:558
    24. 
  
    
    
  
  24. cluster_stats_messages_meet_sent:5
    25. 
  
    
    
  
  25. cluster_stats_messages_sent:1140
    26. 
  
    
    
  
  26. cluster_stats_messages_ping_received:558
    27. 
  
    
    
  
  27. cluster_stats_messages_pong_received:582
    28. 
  
    
    
  
  28. cluster_stats_messages_received:1140
    29. 
  
    
    
  

    30. 
  
    
    
  
  30. [root@qiniu redis-5.0.8]# redis-cli -h 127.0.0.1 -p 7000 cluster nodes
    31. 
  
    
    
  
  31. c28ad47247c7172faeddeebbfbbbcb7bf9f151b0 127.0.0.1:7002@17002 master - 0 1585835417764 4 connected 10923-16383
    32. 
  
    
    
  
  32. 5260ee3591f0a43698d71735dd57a65efb16dd2f 127.0.0.1:7004@17004 slave fb1026c49a5cccd2d18310a5bafd67433538bc78 0 1585835415762 3 connected
    33. 
  
    
    
  
  33. f68ef79fbed0b2faa59227037f99d09ac32295dc 127.0.0.1:7005@17005 slave c28ad47247c7172faeddeebbfbbbcb7bf9f151b0 0 1585835418765 5 connected
    34. 
  
    
    
  
  34. df55c705abff3cc905eefadbc5332a9a59af9597 127.0.0.1:7003@17003 slave fdd63d2dddddbca505b824685f7a03e08d88558b 0 1585835417000 2 connected
    35. 
  
    
    
  
  35. fb1026c49a5cccd2d18310a5bafd67433538bc78 127.0.0.1:7001@17001 master - 0 1585835419767 1 connected 5461-10922
    36. 
  
    
    
  
  36. fdd63d2dddddbca505b824685f7a03e08d88558b 127.0.0.1:7000@17000 myself,master - 0 1585835418000 0 connected 0-5460
    37. 
  
    
    
  

    38. 
  
    
    
  
  38. [root@qiniu redis-5.0.8]# redis-cli -h 127.0.0.1 -p 7000 cluster slots
    39. 
  
    
    
  
  39. 1) 1) (integer) 10923
    40. 
  
    
    
  
  40.  1) (integer) 16383
    41. 
  
    
    
  
  41.  2) 1) "127.0.0.1"
    42. 
  
    
    
  
  42.  1) (integer) 7002
    43. 
  
    
    
  
  43.  2) "c28ad47247c7172faeddeebbfbbbcb7bf9f151b0"
    44. 
  
    
    
  
  44.  3) 1) "127.0.0.1"
    45. 
  
    
    
  
  45.  1) (integer) 7005
    46. 
  
    
    
  
  46.  2) "f68ef79fbed0b2faa59227037f99d09ac32295dc"
    47. 
  
    
    
  
  47. 2) 1) (integer) 5461
    48. 
  
    
    
  
  48.  1) (integer) 10922
    49. 
  
    
    
  
  49.  2) 1) "127.0.0.1"
    50. 
  
    
    
  
  50.  1) (integer) 7001
    51. 
  
    
    
  
  51.  2) "fb1026c49a5cccd2d18310a5bafd67433538bc78"
    52. 
  
    
    
  
  52.  3) 1) "127.0.0.1"
    53. 
  
    
    
  
  53.  1) (integer) 7004
    54. 
  
    
    
  
  54.  2) "5260ee3591f0a43698d71735dd57a65efb16dd2f"
    55. 
  
    
    
  
  55. 3) 1) (integer) 0
    56. 
  
    
    
  
  56.  1) (integer) 5460
    57. 
  
    
    
  
  57.  2) 1) "127.0.0.1"
    58. 
  
    
    
  
  58.  1) (integer) 7000
    59. 
  
    
    
  
  59.  2) "fdd63d2dddddbca505b824685f7a03e08d88558b"
    60. 
  
    
    
  
  60.  3) 1) "127.0.0.1"
    61. 
  
    
    
  
  61.  1) (integer) 7003
    62. 
  
    
    
  
  62.  2) "df55c705abff3cc905eefadbc5332a9a59af9597"
    63.

以上就完成了三主三从的Redis集群配置

redis cluster测试

通过go-redis简单地测试

 
   
   
 
    
  
    
    
  
  1. package main
    2. 
  
    
    
  

    3. 
  
    
    
  
  3. import (
    4. 
  
    
    
  
  4.  "fmt"
    5. 
  
    
    
  
  5.  "github.com/go-redis/redis"
    6. 
  
    
    
  
  6.  "strconv"
    7. 
  
    
    
  
  7. )
    8. 
  
    
    
  

    9. 
  
    
    
  
  9. func main() {
    10. 
  
    
    
  
  10.  //redis cluster
    11. 
  
    
    
  
  11.  rdb := redis.NewClusterClient(&redis.ClusterOptions{
    12. 
  
    
    
  
  12.  Addrs: []string{"192.168.99.128:7000", "192.168.99.129:7001", "192.168.99.130:7002", "192.168.99.130:7003", "192.168.99.129:7004", "192.168.99.128:7005"},
    13. 
  
    
    
  
  13.  Password: "passwd!s",
    14. 
  
    
    
  
  14.  MaxRetries: 4,
    15. 
  
    
    
  
  15.  })
    16. 
  
    
    
  
  16.  for i := 0; i < 1000; i++ {
    17. 
  
    
    
  
  17.  key := "test" + strconv.Itoa(i)
    18. 
  
    
    
  
  18.  err := rdb.Set(key, "set key from golang", 0).Err()
    19. 
  
    
    
  
  19.  //rdb.Process()
    20. 
  
    
    
  
  20.  if err != nil {
    21. 
  
    
    
  
  21.  panic(err)
    22. 
  
    
    
  
  22.  }
    23. 
  
    
    
  
  23.  }
    24. 
  
    
    
  
  24.  fmt.Println("insert data done.")
    25. 
  
    
    
  
  25.  for i := 500; i < 1000; i++ {
    26. 
  
    
    
  
  26.  keys := "test" + strconv.Itoa(i)
    27. 
  
    
    
  
  27.  fmt.Println("keys: ", rdb.ClusterKeySlot(keys))
    28. 
  
    
    
  
  28.  }
    29. 
  
    
    
  
  29. }
    30.

官方方式部署redis-cluster

在Redis 5.0 之后可以通过Redis-cli实现集群的部署与安装

 
   
   
 
    
  
    
    
  
  1. # 首先我们需要提前准备好这些redis实例
    2. 
  
    
    
  
  2. [root@qiniu ~]# redis-cli --cluster create 127.0.0.1:7000 127.0.0.1:7001 127.0.0.1:7002 127.0.0.1:7003 127.0.0.1:7004 127.0.0.1:7005 --cluster-replicas 1
    3. 
  
    
    
  
  3. >>> Performing hash slots allocation on 6 nodes...
    4. 
  
    
    
  
  4. Master[0] -> Slots 0 - 5460
    5. 
  
    
    
  
  5. Master[1] -> Slots 5461 - 10922
    6. 
  
    
    
  
  6. Master[2] -> Slots 10923 - 16383
    7. 
  
    
    
  
  7. Adding replica 127.0.0.1:7004 to 127.0.0.1:7000
    8. 
  
    
    
  
  8. Adding replica 127.0.0.1:7005 to 127.0.0.1:7001
    9. 
  
    
    
  
  9. Adding replica 127.0.0.1:7003 to 127.0.0.1:7002
    10. 
  
    
    
  
  10. >>> Trying to optimize slaves allocation for anti-affinity
    11. 
  
    
    
  
  11. [WARNING] Some slaves are in the same host as their master
    12. 
  
    
    
  
  12. M: ab3f9f295905d3ff113c0cfebc3000ae8d0eb717 127.0.0.1:7000
    13. 
  
    
    
  
  13.  slots:[0-5460] (5461 slots) master
    14. 
  
    
    
  
  14. M: a22ca7f0c97d86a47897694a8e1f48a29702ae72 127.0.0.1:7001
    15. 
  
    
    
  
  15.  slots:[5461-10922] (5462 slots) master
    16. 
  
    
    
  
  16. M: 5f08b2ea3c26ae39843b0bf964bac5a8596e8cda 127.0.0.1:7002
    17. 
  
    
    
  
  17.  slots:[10923-16383] (5461 slots) master
    18. 
  
    
    
  
  18. S: 3712bc46f0fcc14ef4fa8044ad319eee1ddc56c9 127.0.0.1:7003
    19. 
  
    
    
  
  19.  replicates 5f08b2ea3c26ae39843b0bf964bac5a8596e8cda
    20. 
  
    
    
  
  20. S: a34cf5c793e3e606f6fe0c2834d9660cd4b7dcf0 127.0.0.1:7004
    21. 
  
    
    
  
  21.  replicates ab3f9f295905d3ff113c0cfebc3000ae8d0eb717
    22. 
  
    
    
  
  22. S: 88ecb048427276a287504e124ef78dd5b7a6e183 127.0.0.1:7005
    23. 
  
    
    
  
  23.  replicates a22ca7f0c97d86a47897694a8e1f48a29702ae72
    24. 
  
    
    
  
  24. Can I set the above configuration? (type 'yes' to accept): yes
    25. 
  
    
    
  
  25. >>> Nodes configuration updated
    26. 
  
    
    
  
  26. >>> Assign a different config epoch to each node
    27. 
  
    
    
  
  27. >>> Sending CLUSTER MEET messages to join the cluster
    28. 
  
    
    
  
  28. Waiting for the cluster to join
    29. 
  
    
    
  
  29. ...
    30. 
  
    
    
  
  30. >>> Performing Cluster Check (using node 127.0.0.1:7000)
    31. 
  
    
    
  
  31. M: ab3f9f295905d3ff113c0cfebc3000ae8d0eb717 127.0.0.1:7000
    32. 
  
    
    
  
  32.  slots:[0-5460] (5461 slots) master
    33. 
  
    
    
  
  33.  1 additional replica(s)
    34. 
  
    
    
  
  34. S: 88ecb048427276a287504e124ef78dd5b7a6e183 127.0.0.1:7005
    35. 
  
    
    
  
  35.  slots: (0 slots) slave
    36. 
  
    
    
  
  36.  replicates a22ca7f0c97d86a47897694a8e1f48a29702ae72
    37. 
  
    
    
  
  37. S: a34cf5c793e3e606f6fe0c2834d9660cd4b7dcf0 127.0.0.1:7004
    38. 
  
    
    
  
  38.  slots: (0 slots) slave
    39. 
  
    
    
  
  39.  replicates ab3f9f295905d3ff113c0cfebc3000ae8d0eb717
    40. 
  
    
    
  
  40. S: 3712bc46f0fcc14ef4fa8044ad319eee1ddc56c9 127.0.0.1:7003
    41. 
  
    
    
  
  41.  slots: (0 slots) slave
    42. 
  
    
    
  
  42.  replicates 5f08b2ea3c26ae39843b0bf964bac5a8596e8cda
    43. 
  
    
    
  
  43. M: 5f08b2ea3c26ae39843b0bf964bac5a8596e8cda 127.0.0.1:7002
    44. 
  
    
    
  
  44.  slots:[10923-16383] (5461 slots) master
    45. 
  
    
    
  
  45.  1 additional replica(s)
    46. 
  
    
    
  
  46. M: a22ca7f0c97d86a47897694a8e1f48a29702ae72 127.0.0.1:7001
    47. 
  
    
    
  
  47.  slots:[5461-10922] (5462 slots) master
    48. 
  
    
    
  
  48.  1 additional replica(s)
    49. 
  
    
    
  
  49. [OK] All nodes agree about slots configuration.
    50. 
  
    
    
  
  50. >>> Check for open slots...
    51. 
  
    
    
  
  51. >>> Check slots coverage...
    52. 
  
    
    
  
  52. [OK] All 16384 slots covered.
    53. 
  
    
    
  
  53. [root@qiniu ~]# redis-cli -c -p 7000
    54. 
  
    
    
  
  54. 127.0.0.1:7000> cluster info
    55. 
  
    
    
  
  55. cluster_state:ok
    56. 
  
    
    
  
  56. cluster_slots_assigned:16384
    57. 
  
    
    
  
  57. cluster_slots_ok:16384
    58. 
  
    
    
  
  58. cluster_slots_pfail:0
    59. 
  
    
    
  
  59. cluster_slots_fail:0
    60. 
  
    
    
  
  60. cluster_known_nodes:6
    61. 
  
    
    
  
  61. cluster_size:3
    62. 
  
    
    
  
  62. cluster_current_epoch:6
    63. 
  
    
    
  
  63. cluster_my_epoch:1
    64. 
  
    
    
  
  64. cluster_stats_messages_ping_sent:68
    65. 
  
    
    
  
  65. cluster_stats_messages_pong_sent:69
    66. 
  
    
    
  
  66. cluster_stats_messages_sent:137
    67. 
  
    
    
  
  67. cluster_stats_messages_ping_received:64
    68. 
  
    
    
  
  68. cluster_stats_messages_pong_received:68
    69. 
  
    
    
  
  69. cluster_stats_messages_meet_received:5
    70. 
  
    
    
  
  70. cluster_stats_messages_received:137
    71. 
  
    
    
  
  71. 127.0.0.1:7000> cluster nodes
    72. 
  
    
    
  
  72. 88ecb048427276a287504e124ef78dd5b7a6e183 127.0.0.1:7005@17005 slave a22ca7f0c97d86a47897694a8e1f48a29702ae72 0 1585820315000 6 connected
    73. 
  
    
    
  
  73. a34cf5c793e3e606f6fe0c2834d9660cd4b7dcf0 127.0.0.1:7004@17004 slave ab3f9f295905d3ff113c0cfebc3000ae8d0eb717 0 1585820312475 5 connected
    74. 
  
    
    
  
  74. 3712bc46f0fcc14ef4fa8044ad319eee1ddc56c9 127.0.0.1:7003@17003 slave 5f08b2ea3c26ae39843b0bf964bac5a8596e8cda 0 1585820316484 4 connected
    75. 
  
    
    
  
  75. 5f08b2ea3c26ae39843b0bf964bac5a8596e8cda 127.0.0.1:7002@17002 master - 0 1585820315000 3 connected 10923-16383
    76. 
  
    
    
  
  76. a22ca7f0c97d86a47897694a8e1f48a29702ae72 127.0.0.1:7001@17001 master - 0 1585820315481 2 connected 5461-10922
    77. 
  
    
    
  
  77. ab3f9f295905d3ff113c0cfebc3000ae8d0eb717 127.0.0.1:7000@17000 myself,master - 0 1585820314000 1 connected 0-5460
    78. 
  
    
    
  
  78. 127.0.0.1:7000> 
    79. 
  
    
    
  
  79. 127.0.0.1:7000> set hello redis
    80. 
  
    
    
  
  80. OK
    81. 
  
    
    
  
  81. 127.0.0.1:7000> exit
    82. 
  
    
    
  
  82. [root@qiniu ~]# redis-cli -c -p 7001
    83. 
  
    
    
  
  83. 127.0.0.1:7001> get hello
    84. 
  
    
    
  
  84. -> Redirected to slot [866] located at 127.0.0.1:7000
    85. 
  
    
    
  
  85. "redis"
    86. 
  
    
    
  
  86. 127.0.0.1:7000>
    87.


以上是关于到了弃用Redis-sentinel架构的时候了的主要内容，如果未能解决你的问题，请参考以下文章

React native Task :app:processDebugResources FAILED 在此构建中使用了弃用的 Gradle 功能，使其与 Gradle 7.0 不兼容

弃用代码的目的是啥？

Rails 6.1.4 弃用警告：使用“。”呈现操作

在 Rails 4 中使用 has_many :through :uniq 时的弃用警告

Redis-sentinel监控

Redis-sentinel