大家好呀，在上一篇搭建完成Redis集群以后，老哥一直在想挤点时间，把哨兵集群搭好，今天，它来了
给大家带来的是Redis Sentinel(哨兵)集群+分片集群搭建，和上一篇Redis Cluster集群搭建大同小异，不过老哥还是说下它们的区别，最大的区别是自动化，哨兵发现主节点挂了，会自动选举新的节点为主节点
闲话不扯了，开始搭建，这次搭建，需要在上一篇基础上搭建，Linux 部署Redis Cluster 集群，最新教程，细到极致，上述搭建完成以后，开始正式de旅程
1、进入我们编译好的文件夹，然后创建一个log文件夹
[root@VM-4-2-centos redis]# pwd
/usr/local/redis
[root@VM-4-2-centos redis]# mkdir log
[root@VM-4-2-centos redis]# ll
total 8
drwxr-xr-x 2 root root 4096 May 29 09:41 bin
drwxr-xr-x 2 root root 4096 May 29 09:45 conf
drwxr-xr-x 2 root root 4096 May 30 18:35 log
2、复制解压的 sentinel.conf 配置到/usr/local/redis/conf下，然后分发一下配置，不会分发的，可以看我之前mysql分发教程
[root@VM-4-2-centos redis-6.2.7]# cp /opt/redis/redis-6.2.7/sentinel.conf /usr/local/redis/conf
[root@VM-4-2-centos conf]# /opt/mysql/xsync_bin/xsync /usr/local/redis/conf/sentinel.conf
3、修改配置，然后修改以下几个地方，需要注意，sentinel 默认端口是26379,整个配置修改地方比较多，需要耐心
bind是开放任意ip访问,
daemonize 启动后台进程，
requirepass 123456 是密码
sentinel announce-ip，暴露你的公网ip地址，方便后面的集群启动
sentinel monitor mymaster 你的公网ip地址 26379 2，指定主节点信息以及选举master时的quorum值
后面两个是关于超时的配置
#这里设置了主机5秒无响应，则认为挂了
sentinel down-after-milliseconds mymaster 5000
#故障转移的超时时间，这里设置为1分钟。
sentinel failover-timeout mymaster 60000
[root@VM-4-2-centos redis]# vi conf/sentinel.conf
增加了配置内容：日志文件
# bind 127.0.0.1 192.168.1.1
#
# protected-mode no
bind 0.0.0.0
# requirepass <password>
#
requirepass 123456
# By default Redis Sentinel does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis-sentinel.pid when
# daemonized.
daemonize yes
# sentinel auth-pass <master-name> <password>
#
sentinel auth-pass mymaster 123456
#日志文件，生成到log文件夹下
logfile /usr/local/redis/log/sentinel.log
# sentinel announce-ip <ip>
# sentinel announce-port <port>
sentinel announce-ip 你的公网ip地址
# sentinel monitor <master-name> <ip> <redis-port> <quorum>
#注意：这个参数默认开启127.0.0.1，需要找到，然后修改
sentinel monitor mymaster 101.35.245.191 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000
4、分发配置，其他的不修改，只需要修改一下，sentinel announce-ip 你的公网ip地址
[root@VM-4-2-centos redis]# /opt/mysql/xsync_bin/xsync /usr/local/redis/conf/sentinel.conf
5、分别启动三台服务器的RedisCluster,然后启动Redis Sentinel
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis.conf
[root@VM-4-2-centos redis]# ./bin/redis-sentinel ./conf/sentinel.conf
6、查看进程，然后我们尝试连接一下，输入ping命令，没有问题,Sentinel默认端口26379
[root@VM-4-2-centos redis]# ps -ef |grep redis
root 2328908 1 0 21:33 ? 00:00:00 ./bin/redis-sentinel 0.0.0.0:26379 [sentinel]
root 2329869 2313567 0 21:39 pts/0 00:00:00 grep --color=auto redis
[root@VM-4-2-centos redis]# ./bin/redis-cli -p 26379
127.0.0.1:26379> ping
PONG
7、查看哨兵相关信息，slaves=2,sentinels=3，说明搭建成功！
127.0.0.1:26379> info sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=mymaster,status=ok,address=101.35.245.191:6379,slaves=2,sentinels=3
8、在哨兵模式下，主节点发生故障，Raft算法会选举新的节点成为主节点，我们测试一下
切换到第一台服务器:
[root@VM-4-2-centos redis]# ps -ef |grep redis
root 2358654 1 0 01:04 ? 00:00:01 ./bin/redis-server 0.0.0.0:6379 [cluster]
root 2361715 2313567 0 01:26 pts/0 00:00:00 grep --color=auto redis
[root@VM-4-2-centos redis]# kill -9 2358654
主节点挂掉以后，我们查看从节点信息
切换到第二台服务器:
[root@VM-4-12-centos redis]# ./bin/redis-cli -p 26379
127.0.0.1:26379> info sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=mymaster,status=ok,address=124.222.204.94:6379,slaves=2,sentinels=3
9、我们可以发现，主节点已经切换了，address=124.222.204.94:6379，到此，整个哨兵集群搭建完毕
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------>
10、接下来是我们的分片集群，首先需要知道为什么需要分片集群
11、关掉所有的Redis进程，发现使用kill -9命令杀掉，每台服务器一样
[root@VM-4-2-centos redis]# ps -ef |grep redis
root 2430255 2313567 0 09:45 pts/0 00:00:00 grep --color=auto redis
12、然后我们删除conf/redis.conf,因为我们需要重新配置Redis.conf文件，保证数据干净，三台服务器一样
[root@VM-4-2-centos redis]# rm -rf conf/redis.conf
13、重新拷贝一份 redis.conf 配置文件，分发配置
[root@VM-4-2-centos redis]# cp /opt/redis/redis-6.2.7/redis.conf /usr/local/redis/conf/
[root@VM-4-2-centos redis]# /opt/mysql/xsync_bin/xsync /usr/local/redis/conf/redis.conf
14、修改配置，cluster-config-file 特别注意这个，每台机器每个节点都不一样哦
[root@VM-4-2-centos redis]# vi conf/redis.conf
# 开启集群功能
# cluster-enabled yes
cluster-enabled yes
# 集群的配置文件名称，建议格式nodes-第几台-端口
# cluster-config-file nodes-6379.conf
cluster-config-file /usr/local/redis/nodes-1-6379.conf
# 节点心跳失败的超时时间
# cluster-node-timeout 15000
cluster-node-timeout 5000
# 开放任意端口
#bind 127.0.0.1 -::1
bind 0.0.0.0
# 让redis后台运行
daemonize yes
# replica-announce-ip 5.5.5.5
# replica-announce-port 1234
# 暴露当前实例ip
replica-announce-ip 101.35.245.191
#日志文件
logfile /usr/local/redis/log/cluster.log
15、分发配置，其他的不修改，只需要修改一下，replica-announce-ip 你的公网ip地址
[root@VM-4-2-centos redis]# /opt/mysql/xsync_bin/xsync /usr/local/redis/conf/redis.conf
16、然后老哥的想法是这样的，每台机器两个节点，端口分别为6379 6380，一共6个节点
[root@VM-4-2-centos redis]# cp conf/redis.conf conf/redis-6380.conf
[root@VM-4-2-centos redis]# cd conf/
[root@VM-4-2-centos conf]# ll
total 200
-rw-r--r-- 1 root root 94030 May 31 10:21 redis-6380.conf
-rw-r--r-- 1 root root 94030 May 31 10:09 redis.conf
-rw-r--r-- 1 root root 14332 May 31 01:13 sentinel.conf
17、修改配置，分发
[root@VM-4-2-centos conf]# vi redis-6380.conf
# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
port 6380
pidfile /var/run/redis_6380.pid
# cluster-config-file nodes-6379.conf
cluster-config-file /usr/local/redis/nodes-1-6380.conf
[root@VM-4-2-centos redis]# /opt/mysql/xsync_bin/xsync /usr/local/redis/conf/redis-6380.conf
18、分别启动，每台服务器，每个节点，如果报错了，可以去查看一下log文件夹下的日志
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis.conf
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis-6380.conf
19、查看状态，没有任何问题
[root@VM-4-2-centos redis]# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1729/sshd
tcp 0 0 0.0.0.0:16379 0.0.0.0:* LISTEN 2436198/./bin/redis
tcp 0 0 0.0.0.0:16380 0.0.0.0:* LISTEN 2441449/./bin/redis
tcp 0 0 0.0.0.0:6379 0.0.0.0:* LISTEN 2436198/./bin/redis
tcp 0 0 0.0.0.0:6380 0.0.0.0:* LISTEN 2441449/./bin/redis
tcp6 0 0 :::22
[root@VM-4-2-centos redis]# ps -ef |grep redis
root 2436198 1 0 10:27 ? 00:00:00 ./bin/redis-server 0.0.0.0:6379 [cluster]
root 2441449 1 0 10:33 ? 00:00:00 ./bin/redis-server 0.0.0.0:6380 [cluster]
root 2445887 2313567 0 10:35 pts/0 00:00:00 grep --color=auto redis
You have mail in /var/spool/mail/root
20、现在我们6个节点都已经起来了，但是没有分片，也没有分Hash槽，都是单节点，接下来，需要连成一条线。
redis-cli --cluster或者./redis-trib.rb：代表集群操作命令create：代表是创建集群--replicas 1或者--cluster-replicas 1：指定集群中每个master的副本个数为1，此时节点总数 ÷ (replicas + 1)得到的就是master的数量。因此节点列表中的前n个就是master，其它节点都是slave节点，随机分配到不同master
注意：创建前，需要kill关闭各节点，同时清空rdb和node.conf文件，然后再次启动,否则会报错
[ERR] Node 101.34.7.236:6379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.
[root@VM-4-2-centos redis]# rm -rf dump.rdb
[root@VM-4-2-centos redis]# rm -rf nodes*
重新启动各节点：
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis.conf
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis-6380.conf
./bin/redis-cli --cluster create --cluster-replicas 1 101.35.245.191:6381 101.34.7.236:6379 124.222.204.94:6379 101.35.245.191:6382 101.34.7.236:6380 124.222.204.94:6380
21、创建节点中，输入一次 yes
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 101.34.7.236:6380 to 101.35.245.191:6381
Adding replica 124.222.204.94:6380 to 101.34.7.236:6379
Adding replica 101.35.245.191:6382 to 124.222.204.94:6379
M: 6ccf3b25ea95e3e585ba86b5b68307e49b5cd137 101.35.245.191:6381
slots:[0-5460] (5461 slots) master
M: d08eaf2ab32209519c756f548f32e596efb34345 101.34.7.236:6379
slots:[5461-10922] (5462 slots) master
M: 1e5ee1397cf19fd17e29071c8ad7e385740a7de0 124.222.204.94:6379
slots:[10923-16383] (5461 slots) master
S: 2f67443f8573a42221345d68c7fdc31dec7e0202 101.35.245.191:6382
replicates 1e5ee1397cf19fd17e29071c8ad7e385740a7de0
S: f656cc01ce517619cb53c945dcf44ca8263ecaf0 101.34.7.236:6380
replicates 6ccf3b25ea95e3e585ba86b5b68307e49b5cd137
S: e88a401ac460e8eb8f60a542c55db72a3a4ae09e 124.222.204.94:6380
replicates d08eaf2ab32209519c756f548f32e596efb34345
Can I set the above configuration? (type 'yes' to accept): yes
22、然后记得开放云服务器端口 16379 16380，一定要记得，否则会一直 Waiting for the cluster to join
>>> Performing Cluster Check (using node 101.35.245.191:6379)
M: cc572bd57fd4a3a5b0e64bf400fc3784da1ea8a4 101.35.245.191:6379
slots:[0-5460] (5461 slots) master
1 additional replica(s)
M: 5381702d4e5ab64bb1cf8d6e369d8c940ae40232 124.222.204.94:6381
slots:[10923-16383] (5461 slots) master
1 additional replica(s)
S: 52d0b13dfcb8705fe17ac0c9b94bb83d2662b0ba 101.34.7.236:6380
slots: (0 slots) slave
replicates cc572bd57fd4a3a5b0e64bf400fc3784da1ea8a4
S: 6b0fb6e6364a4733106be5f2e408c6ae46981d8b 124.222.204.94:6380
slots: (0 slots) slave
replicates a7b7064437f813a00c877a9ee76107c71fcbe4f7
M: a7b7064437f813a00c877a9ee76107c71fcbe4f7 101.34.7.236:6379
slots:[5461-10922] (5462 slots) master
1 additional replica(s)
S: 07aaed5cd150cae564ac68925931fbcd47747490 101.35.245.191:6380
slots: (0 slots) slave
replicates 5381702d4e5ab64bb1cf8d6e369d8c940ae40232
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
23、然后我们通过命令可以查看集群状态，我们可以看到，6379、6381都是主节点，6380都是从节点
[root@VM-4-2-centos redis]# ./bin/redis-cli -p 6379
127.0.0.1:6379> cluster nodes
5381702d4e5ab64bb1cf8d6e369d8c940ae40232 124.222.204.94:6381@16381 master - 0 1654000004000 3 connected 10923-16383
52d0b13dfcb8705fe17ac0c9b94bb83d2662b0ba 101.34.7.236:6380@16380 slave cc572bd57fd4a3a5b0e64bf400fc3784da1ea8a4 0 1654000004000 1 connected
cc572bd57fd4a3a5b0e64bf400fc3784da1ea8a4 10.0.4.2:6379@16379 myself,master - 0 1654000004000 1 connected 0-5460
6b0fb6e6364a4733106be5f2e408c6ae46981d8b 124.222.204.94:6380@16380 slave a7b7064437f813a00c877a9ee76107c71fcbe4f7 0 1654000004633 2 connected
a7b7064437f813a00c877a9ee76107c71fcbe4f7 101.34.7.236:6379@16379 master - 0 1654000003629 2 connected 5461-10922
07aaed5cd150cae564ac68925931fbcd47747490 101.35.245.191:6380@16380 slave 5381702d4e5ab64bb1cf8d6e369d8c940ae40232 0 1654000005035 3 connected
24、然后我们进行赋值操作，这里需要注意的是，分片集群客户端命令，需要加一个-c,代表分片集群模式访问，否则无法赋值操作
[root@VM-4-2-centos redis]# ./bin/redis-cli -c -p 6379
127.0.0.1:6379> set aa Jessica
OK
切换到第二台服务器，成功拿到参数，而且，我们可以注意到，参数是在Hash槽 1180拿到的
127.0.0.1:6379> get aa
-> Redirected to slot [1180] located at 101.35.245.191:6379
"Jessica"
25、然后我们会发现，上面无论是set get 都有Redirected ,重定向，其实，这非常消耗性能，我们可以通过{},将同一类数据放在一个节点上，避免频繁换槽
127.0.0.1:6379> set a 1
-> Redirected to slot [15495] located at 124.222.204.94:6381
OK
124.222.204.94:6381> set {a}num 111
OK
124.222.204.94:6381> set {a}num2 222
OK
124.222.204.94:6381> get {a}num
"111"
124.222.204.94:6381> get {a}num2
"222"
26、然后我们测试分片集群-动态收缩，复制一份配置文件，新增一个节点，动态收缩，简单来说，就是，程序运行时，任意增加一个节点，或者减少一个节点，不对数据造成影响
sed -i s/6380/6386/g conf/redis-6386.conf，这条命令我需要解释一下，sed -i 发送，s修改/当前内容/修改后内容，g全局替换，后面是具体的文件路径+文件名，其实就是相当于用命令行，去修改配置文件
[root@VM-4-2-centos redis]# cp conf/redis-6380.conf conf/redis-6386.conf
[root@VM-4-2-centos redis]# sed -i s/6380/6386/g conf/redis-6386.conf
27、启动新节点，同时开放服务器端口6386,16386
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis-6386.conf
28、添加节点到 分片集群，前面ip+端口是你要添加的节点信息，后面是集群任意一个节点，这就好比，你要去别人家做客，是不是要先告诉主人公一声，我要去你家蹭饭
[root@VM-4-2-centos redis]# ./bin/redis-cli --cluster add-node 101.35.245.191:6386 101.35.245.191:6379
29、查看一下，我们可以看到，6386节点成功加入！
[root@VM-4-2-centos redis]# ./bin/redis-cli -p 6379
127.0.0.1:6379> cluster nodes
e7104735b9bd2a7fd0d03c50cf47ae4436e505d8 10.0.4.2:6379@16379 myself,master - 0 1654007742000 1 connected 0-5460
f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 101.34.7.236:6379@16379 master - 0 1654007744126 2 connected 5461-10922
235216b9633bac63adfa6fb66b8b99aa89b74b61 101.35.245.191:6386@16386 master - 0 1654007743000 0 connected
f8ea86c29b7244e4493a691de5d30723c8b86bfa 124.222.204.94:6381@16381 master - 0 1654007743023 3 connected 10923-16383
9d5493808ad159da937fd6e5d4bb18e2bafd24be 124.222.204.94:6380@16380 slave f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 0 1654007743000 2 connected
5026c23290ada3b3e5b6a50b31f8cada12fd0405 101.34.7.236:6380@16380 slave e7104735b9bd2a7fd0d03c50cf47ae4436e505d8 0 1654007743124 1 connected
5696396d9b257b1a170c79738854cb16ccd2eeba 101.35.245.191:6380@16380 slave f8ea86c29b7244e4493a691de5d30723c8b86bfa 0 1654007743524 3 connected
30、我们随便设置一个值num，然后将num迁移到新节点,思路是这样的，num现在在 101.35.245.191:6379 第2765槽位上，那么我们需要从6379中，取走0-2765的槽位，才能把num移动到6386节点上
[root@VM-4-2-centos redis]# ./bin/redis-cli -c -p 6379
127.0.0.1:6379> set num 123
OK
切换到第二台服务器：
124.222.204.94:6381> get num
-> Redirected to slot [2765] located at 101.35.245.191:6379
"123"
31、然后我们重新局部分片，给一点槽位给到6386，分配3000个槽位，然后给到6386的实例ID
然后，下面填，你要发送的实例ID，就是发送方，done是确认这样做
32、查看节点信息，我们可以清楚的看到，0到2999 插槽在6386节点上，
[root@VM-4-2-centos redis]# ./bin/redis-cli -p 6379 cluster nodes
33、切换到第二台服务器，当我们再次获取num时，发现它已经在6386节点上
[root@VM-4-12-centos redis]# ./bin/redis-cli -c -p 6379
101.35.245.191:6379> get num
-> Redirected to slot [2765] located at 101.35.245.191:6386
"123"
34、然后接着，我们测试故障迁移，我们手动把第二台服务器，6379节点下线,6380成为新的主节点
[root@VM-4-2-centos redis]# ./bin/redis-cli -p 6379
127.0.0.1:6379> shutdown
127.0.0.1:6379> cluster nodes
5026c23290ada3b3e5b6a50b31f8cada12fd0405 101.34.7.236:6380@16380 master - 0 1654009788989 8 connected 3000-5460
9d5493808ad159da937fd6e5d4bb18e2bafd24be 124.222.204.94:6380@16380 slave f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 0 1654009787578 2 connected
f8ea86c29b7244e4493a691de5d30723c8b86bfa 124.222.204.94:6381@16381 master - 0 1654009788000 3 connected 10923-16383
f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 101.34.7.236:6379@16379 master,fail? - 1654009783544 1654009781000 2 disconnected 5461-10922
5696396d9b257b1a170c79738854cb16ccd2eeba 101.35.245.191:6380@16380 slave f8ea86c29b7244e4493a691de5d30723c8b86bfa 0 1654009788000 3 connected
e7104735b9bd2a7fd0d03c50cf47ae4436e505d8 10.0.4.2:6379@16379 myself,slave 5026c23290ada3b3e5b6a50b31f8cada12fd0405 0 1654009786000 8 connected
235216b9633bac63adfa6fb66b8b99aa89b74b61 101.35.245.191:6386@16386 master - 0 1654009787000 7 connected 0-2999
35、然后我们重新恢复，101.34.7.236:6379 节点，发现它已经是slave
[root@VM-4-2-centos redis]# ./bin/redis-server ./conf/redis.conf
127.0.0.1:6379> cluster nodes
5026c23290ada3b3e5b6a50b31f8cada12fd0405 101.34.7.236:6380@16380 master - 0 1654009897000 8 connected 3000-5460
9d5493808ad159da937fd6e5d4bb18e2bafd24be 124.222.204.94:6380@16380 master - 0 1654009897000 9 connected 5461-10922
f8ea86c29b7244e4493a691de5d30723c8b86bfa 124.222.204.94:6381@16381 master - 0 1654009898000 3 connected 10923-16383
f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 101.34.7.236:6379@16379 slave 9d5493808ad159da937fd6e5d4bb18e2bafd24be 0 1654009898710 9 connected
5696396d9b257b1a170c79738854cb16ccd2eeba 101.35.245.191:6380@16380 slave f8ea86c29b7244e4493a691de5d30723c8b86bfa 0 1654009898000 3 connected
e7104735b9bd2a7fd0d03c50cf47ae4436e505d8 10.0.4.2:6379@16379 myself,slave 5026c23290ada3b3e5b6a50b31f8cada12fd0405 0 1654009897000 8 connected
235216b9633bac63adfa6fb66b8b99aa89b74b61 101.35.245.191:6386@16386 master - 0 1654009898509 7 connected 0-2999
36、最后，我们将6379节点，重新夺权，拿回属于自己的地位
[root@VM-4-12-centos redis]# ./bin/redis-server ./conf/redis.conf
[root@VM-4-12-centos redis]# ./bin/redis-cli -c -p 6379
127.0.0.1:6379> CLUSTER FAILOVER
OK
127.0.0.1:6379> cluster nodes
5026c23290ada3b3e5b6a50b31f8cada12fd0405 101.34.7.236:6380@16380 master - 0 1654010331395 8 connected 3000-5460
9d5493808ad159da937fd6e5d4bb18e2bafd24be 124.222.204.94:6380@16380 slave f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 0 1654010330000 12 connected
f8ea86c29b7244e4493a691de5d30723c8b86bfa 124.222.204.94:6381@16381 master - 0 1654010329388 3 connected 10923-16383
f00c3aa3bc36755f1110f8fc5e3099c274f2a1c2 101.34.7.236:6379@16379 master - 0 1654010330593 12 connected 5461-10922
5696396d9b257b1a170c79738854cb16ccd2eeba 101.35.245.191:6380@16380 slave f8ea86c29b7244e4493a691de5d30723c8b86bfa 0 1654010330592 3 connected
e7104735b9bd2a7fd0d03c50cf47ae4436e505d8 10.0.4.2:6379@16379 myself,slave 5026c23290ada3b3e5b6a50b31f8cada12fd0405 0 1654010331000 8 connected
235216b9633bac63adfa6fb66b8b99aa89b74b61 101.35.245.191:6386@16386 master - 0 1654010330392 7 connected 0-2999
37、看到这里，麻烦给老哥一个点赞、关注、收藏三连好吗，你的支持是老哥更新最大的动力，谢谢！
3万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
