使用三主三副的模式对Redis 6.2.4进行集群搭建

原创已于 2023-11-08 14:29:50 修改 · 865 阅读

2 ·

CC 4.0 BY-SA版权

文章标签：

#redis #数据库

于 2023-06-28 14:36:26 首次发布

架构专栏收录该内容

16 篇文章

订阅专栏

该文详细介绍了如何在没有哨兵模式的情况下搭建Redis集群，包括配置文件设置、启动命令、集群状态检查以及SpringBoot应用程序的连接配置。文中还提到了集群的端口策略和在MacOS上的安装方法，并给出了一段日志示例，展示了集群在节点故障后的自我修复过程。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

1. 说明

这里使用的是redis的cluster集群模式，没有用哨兵模式（哨兵模式依赖哨兵节点，哨兵节点一旦挂掉就不再高可用了，因此没有采用）。
由于Redis Cluster至少需要6个节点，因此，这里咱们采用的是三主三副的模式。redis的key值通过hash计算会散列在3个主节点中，副节点跟相应主节点保持一致。
在这里插入图片描述

2. Redis相关配置

这里咱们用6380~6385这6个实例标识6个节点的端口，修改相关配置：

#端口号
port 6380
#默认ip为127.0.0.1，需要改为其他节点机器可以访问的ip，否则创建集群时无法访问对应的端口，无法创建集群（使用#注掉bind则任何地址都可访问）
bind 192.168.9.128
#redis后台运行
daemonize yes
#pidfile文件对应6380,6381,6382…
pidfile /var/run/redis_6380.pid
#开启集群
cluster-enabled yes
#集群的配置，配置文件首次启动自动生成6380,6381,6382…
cluster-config-file nodes_6380.conf
#请求超时，默认15秒，可自行设置
cluster-node-timeout 15000
#aof日志开启，有需要就开启，它会每次写操作都记录一条日志
appendonly yes
# 密码保持相同
requirepass 123456
# 日志可以配置下，方便问题查找
#logfile 6380.log
# 主节点密码
masterauth 123456

创建6个文件夹，6380~6385，将redis.conf拷贝到这6个文件夹下，并修改以下配置：

#端口号
port 6380
#pidfile文件对应6380,6381,6382…
pidfile /var/run/redis_6380.pid
#集群的配置，配置文件首次启动自动生成6380,6381,6382…
cluster-config-file nodes_6380.conf

将6个节点全部启动：

./src/redis-server 6380/redis.conf &
./src/redis-server 6381/redis.conf &
./src/redis-server 6382/redis.conf &
./src/redis-server 6383/redis.conf &
./src/redis-server 6384/redis.conf &
./src/redis-server 6385/redis.conf &

3. 启动集群

进入src目录，启动集群：

./redis-cli --cluster create 172.17.104.98:6380 172.17.104.98:6381 172.17.104.98:6382 172.17.104.98:6383 172.17.104.98:6384 172.17.104.98:6385 --cluster-replicas 1 -a 123456

这里不要用127.0.0.1的IP，这样配置会产生springboot项目连不上的情况，springboot连上之后，会获取这个集群信息，再用这个信息去连redis。因为你应用和集群不在一台机器上，有可能导致应用连接不上。其中-a表示其他redis的密码。

4. 集群查看

可以使用cluster info查看集群健康状态，cluster nodes查看集群节点状态。

# 命令中 -c表示集群
[root@localhost src]# ./redis-cli -h 127.0.0.1 -c -p 6380 -a 123456
127.0.0.1:6380> 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:5910
cluster_stats_messages_pong_sent:6303
cluster_stats_messages_fail_sent:12
cluster_stats_messages_sent:12225
cluster_stats_messages_ping_received:6303
cluster_stats_messages_pong_received:5903
cluster_stats_messages_fail_received:6
cluster_stats_messages_received:12212
127.0.0.1:6380> cluster nodes
6fa6f4422ff23e39ff5193ff5e53cfdce4f9d5de 172.17.104.98:6383@16383 slave a565cd8244c999e1626b6ba8b76d88bd37059e39 0 1687923362095 1 connected
196b18542407cc079d1fbd8f3d611dc476df0ba8 172.17.104.98:6381@16381 master - 0 1687923359076 2 connected 5461-10922
db7aa96d4cebdd36555216bc4880e6290f185e8b 172.17.104.98:6385@16385 slave 2619026bf36cb586563e20dde244101f7905641f 0 1687923360082 3 connected
2619026bf36cb586563e20dde244101f7905641f 172.17.104.98:6382@16382 master - 0 1687923361088 3 connected 10923-16383
db7698a106d3f09d51dcd0e80dccedc8d58a9d9f 172.17.104.98:6384@16384 slave 196b18542407cc079d1fbd8f3d611dc476df0ba8 0 1687923359000 2 connected
a565cd8244c999e1626b6ba8b76d88bd37059e39 172.17.104.98:6380@16380 myself,master - 0 1687923361000 1 connected 0-5460
127.0.0.1:6380>

当在不同机器上，主从节点会分配到不同主机，尽量减少宕机影响。
在这里插入图片描述

5. SpringBoot连接集群

springboot中的配置，由于这里只可以配置一个password，因此需要集群的所有密码都是相同设置，否则连不上redis报错！

# spring配置
spring:
  redis:
    cluster:
      nodes: 172.17.104.98:6380,172.17.104.98:6381,172.17.104.98:6382,172.17.104.98:6383,172.17.104.98:6384,172.17.104.98:6385
    password: 123456

6. 删除集群

[root@localhost redis-6.2.4]# ls
00-RELEASENOTES  6382  6385            CONDUCT       deps      Makefile         nodes-6381.conf  nodes-6384.conf  redis.conf       runtest-moduleapi  src     utils
6380             6383  appendonly.aof  CONTRIBUTING  dump.rdb  MANIFESTO        nodes-6382.conf  nodes-6385.conf  runtest          runtest-sentinel   tests
6381             6384  BUGS            COPYING       INSTALL   nodes-6380.conf  nodes-6383.conf  README.md        runtest-cluster  sentinel.conf      TLS.md
[root@localhost redis-6.2.4]#

停掉redis所有节点，将所有的nodes-638*的文件都删除，集群将不复存在。

附1. MacOS上如何安装redis

这部分是服务下使用mac系统的小朋友，其实也可以参考官网：https://redis.io/docs/getting-started/installation/install-redis-on-mac-os/

1. 安装redis

# 安装命令
% brew install redis
# 安装完成之后会提示你如何启动，其实也是间接告诉你配置文件在哪里
To start redis now and restart at login:
  brew services start redis
Or, if you don't want/need a background service you can just run:
  /usr/local/opt/redis/bin/redis-server /usr/local/etc/redis.conf

2. 启动

mac@iMac RuoYi-Cloud % brew services start redis
==> Tapping homebrew/services
Cloning into '/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services'...
remote: Enumerating objects: 2470, done.
remote: Counting objects: 100% (291/291), done.
remote: Compressing objects: 100% (110/110), done.
remote: Total 2470 (delta 203), reused 206 (delta 181), pack-reused 2179
Receiving objects: 100% (2470/2470), 681.34 KiB | 1.64 MiB/s, done.
Resolving deltas: 100% (1142/1142), done.
Tapped 1 command (45 files, 850.6KB).
==> Successfully started `redis` (label: homebrew.mxcl.redis)

附2. 端口策略

每个Redis集群中的节点都需要打开两个TCP连接。一个连接用于正常的给Client提供服务，比如6379，还有一个额外的端口（通过在这个端口号上加10000）作为数据端口，比如16379。第二个端口（本例中就是16379）用于集群总线，这是一个用二进制协议的点对点通信信道。这个集群总线（Cluster bus）用于节点的失败侦测、配置更新、故障转移授权，等等。客户端从来都不应该尝试和这些集群总线端口通信，它们只应该和正常的Redis命令端口进行通信。注意，确保在你的防火墙中开放着两个端口，否则，Redis集群节点之间将无法通信。

附3. 参考日志

这个日志演示了一个从启动集群，到两次发生手动挂掉一个主节点、集群自动刷新成功的过程。大家凑合着看吧：

36775:C 23 Aug 2023 15:32:51.684 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
36775:C 23 Aug 2023 15:32:51.684 # Redis version=6.2.4, bits=64, commit=00000000, modified=0, pid=36775, just started
36775:C 23 Aug 2023 15:32:51.684 # Configuration loaded
36775:M 23 Aug 2023 15:32:51.685 * monotonic clock: POSIX clock_gettime
36775:M 23 Aug 2023 15:32:51.686 * Node configuration loaded, I'm e6e31abc81cc5d70307786dfd181ef699f24ef43
36775:M 23 Aug 2023 15:32:51.686 * Running mode=cluster, port=6382.
36775:M 23 Aug 2023 15:32:51.686 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn i
s set to the lower value of 128.
36775:M 23 Aug 2023 15:32:51.686 # Server initialized
36775:M 23 Aug 2023 15:32:51.686 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fi
x this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' f
or this to take effect.
36775:M 23 Aug 2023 15:32:51.687 * Ready to accept connections
36775:M 23 Aug 2023 16:19:57.783 # IP address for this node updated to 10.201.246.16
36775:M 23 Aug 2023 16:19:58.691 # Cluster state changed: ok
36775:M 23 Aug 2023 16:19:59.760 * Replica 10.201.246.17:6385 asks for synchronization
36775:M 23 Aug 2023 16:19:59.760 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for '7097c96a0ffd9
72a7d94d2c291f746aa869d6c3b', my replication IDs are '90a3fd307dcebc46f84e36fd530e8308acc5f634' and '0000000000000000000000000000000
000000000')
36775:M 23 Aug 2023 16:19:59.760 * Replication backlog created, my new replication IDs are '7989e19cf8025f33d2f0df7f83bc9aac38d1f5af
' and '0000000000000000000000000000000000000000'
36775:M 23 Aug 2023 16:19:59.760 * Starting BGSAVE for SYNC with target: disk
36775:M 23 Aug 2023 16:19:59.763 * Background saving started by pid 58891
58891:C 23 Aug 2023 16:19:59.766 * DB saved on disk
58891:C 23 Aug 2023 16:19:59.767 * RDB: 4 MB of memory used by copy-on-write
36775:M 23 Aug 2023 16:19:59.783 * Background saving terminated with success
36775:M 23 Aug 2023 16:19:59.784 * Synchronization with replica 10.201.246.17:6385 succeeded
63020:C 23 Aug 2023 16:28:43.305 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
63020:C 23 Aug 2023 16:28:43.305 # Redis version=6.2.4, bits=64, commit=00000000, modified=0, pid=63020, just started
63020:C 23 Aug 2023 16:28:43.305 # Configuration loaded
63020:M 23 Aug 2023 16:28:43.307 * monotonic clock: POSIX clock_gettime
63020:M 23 Aug 2023 16:28:43.308 * Node configuration loaded, I'm e6e31abc81cc5d70307786dfd181ef699f24ef43
63020:M 23 Aug 2023 16:28:43.308 * Running mode=cluster, port=6382.
63020:M 23 Aug 2023 16:28:43.308 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn i
s set to the lower value of 128.
63020:M 23 Aug 2023 16:28:43.308 # Server initialized
63020:M 23 Aug 2023 16:28:43.308 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fi
x this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' f
or this to take effect.
63020:M 23 Aug 2023 16:28:43.309 * Reading RDB preamble from AOF file...
63020:M 23 Aug 2023 16:28:43.309 * Loading RDB produced by version 6.2.4
63020:M 23 Aug 2023 16:28:43.309 * RDB age 524 seconds
63020:M 23 Aug 2023 16:28:43.309 * RDB memory usage when created 2.50 Mb
63020:M 23 Aug 2023 16:28:43.309 * RDB has an AOF tail
63020:M 23 Aug 2023 16:28:43.309 * Reading the remaining AOF tail...
63020:M 23 Aug 2023 16:28:43.309 * DB loaded from append only file: 0.000 seconds
63020:M 23 Aug 2023 16:28:43.309 * Ready to accept connections
63020:M 23 Aug 2023 16:28:43.310 # Configuration change detected. Reconfiguring myself as a replica of ea5a17aa5092e9c814a7a6371ceb7
2cf5bbdf3ae
63020:S 23 Aug 2023 16:28:43.310 * Before turning into a replica, using my own master parameters to synthesize a cached master: I ma
y be able to synchronize with the new master with just a partial transfer.
63020:S 23 Aug 2023 16:28:43.310 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:28:43.310 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:28:43.310 # Cluster state changed: ok
63020:S 23 Aug 2023 16:28:43.313 * Non blocking connect for SYNC fired the event.
63020:S 23 Aug 2023 16:28:43.313 * Master replied to PING, replication can continue...
63020:S 23 Aug 2023 16:28:43.316 * Trying a partial resynchronization (request 180c88209955eb061eb02fef5f426805e474e078:1).
63020:S 23 Aug 2023 16:28:43.317 * Full resync from master: dbc3411351a45a2678799cfb23001429a1ce3396:574
63020:S 23 Aug 2023 16:28:43.317 * Discarding previously cached master state.
63020:S 23 Aug 2023 16:28:43.412 * MASTER <-> REPLICA sync: receiving 176 bytes from master to disk
63020:S 23 Aug 2023 16:28:43.412 * MASTER <-> REPLICA sync: Flushing old data
63020:S 23 Aug 2023 16:28:43.412 * MASTER <-> REPLICA sync: Loading DB in memory
63020:S 23 Aug 2023 16:28:43.414 * Loading RDB produced by version 6.2.4
63020:S 23 Aug 2023 16:28:43.414 * RDB age 0 seconds
63020:S 23 Aug 2023 16:28:43.414 * RDB memory usage when created 2.54 Mb
63020:S 23 Aug 2023 16:28:43.414 * MASTER <-> REPLICA sync: Finished with success
63020:S 23 Aug 2023 16:28:43.415 * Background append only file rewriting started by pid 63025
63020:S 23 Aug 2023 16:28:43.439 * AOF rewrite child asks to stop sending diffs.
63025:C 23 Aug 2023 16:28:43.439 * Parent agreed to stop sending diffs. Finalizing AOF...
63025:C 23 Aug 2023 16:28:43.439 * Concatenating 0.00 MB of AOF diff received from parent.
63025:C 23 Aug 2023 16:28:43.439 * SYNC append only file rewrite performed
63025:C 23 Aug 2023 16:28:43.440 * AOF rewrite: 2 MB of memory used by copy-on-write
63020:S 23 Aug 2023 16:28:43.511 * Background AOF rewrite terminated with success
63020:S 23 Aug 2023 16:28:43.511 * Residual parent diff successfully flushed to the rewritten AOF (0.00 MB)
63020:S 23 Aug 2023 16:28:43.512 * Background AOF rewrite finished successfully
63020:S 23 Aug 2023 16:30:24.660 # Connection with master lost.
63020:S 23 Aug 2023 16:30:24.660 * Caching the disconnected master state.
63020:S 23 Aug 2023 16:30:24.660 * Reconnecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:24.660 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:24.660 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:25.664 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:25.664 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:25.665 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:26.671 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:26.671 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:26.671 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:27.677 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:27.677 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:27.677 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:28.684 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:28.684 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:28.684 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:29.689 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:29.690 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:29.690 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:30.695 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:30.696 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:30.696 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:31.703 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:31.703 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:31.703 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:32.709 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:32.709 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:32.709 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:33.715 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:33.715 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:33.715 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:34.721 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:34.721 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:34.721 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:35.727 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:35.727 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:35.727 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:36.733 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:36.733 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:36.734 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:37.740 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:37.740 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:37.740 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:38.746 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:38.746 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:38.746 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:39.752 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:39.752 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:39.752 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:40.759 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:40.759 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:40.759 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:41.766 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:41.766 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:41.766 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:42.772 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:42.772 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:42.772 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:43.779 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:43.779 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:43.779 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:44.785 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:44.785 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:44.786 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:45.792 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:45.792 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:45.792 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:46.798 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:46.798 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:46.798 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:46.812 * FAIL message received from d0ed4c3bd82aab1f601fe8f7e1142ac6a0d972ba about ea5a17aa5092e9c814a7a63
71ceb72cf5bbdf3ae
63020:S 23 Aug 2023 16:30:46.812 # Cluster state changed: fail
63020:S 23 Aug 2023 16:30:46.899 # Start of election delayed for 981 milliseconds (rank #0, offset 714).
63020:S 23 Aug 2023 16:30:47.805 * Connecting to MASTER 10.201.246.17:6385
63020:S 23 Aug 2023 16:30:47.805 * MASTER <-> REPLICA sync started
63020:S 23 Aug 2023 16:30:47.805 # Error condition on socket for SYNC: Connection refused
63020:S 23 Aug 2023 16:30:47.905 # Starting a failover election for epoch 8.
63020:S 23 Aug 2023 16:30:47.911 # Failover election won: I'm the new master.
63020:S 23 Aug 2023 16:30:47.911 # configEpoch set to 8 after successful failover
63020:M 23 Aug 2023 16:30:47.911 * Discarding previously cached master state.
63020:M 23 Aug 2023 16:30:47.911 # Setting secondary replication ID to dbc3411351a45a2678799cfb23001429a1ce3396, valid up to offset:
 715. New replication ID is 642621fae8265d57501adcb400e91572c8a4cc58
63020:M 23 Aug 2023 16:30:47.911 # Cluster state changed: ok
63020:M 23 Aug 2023 16:31:46.274 * Replica 10.201.246.17:6385 asks for synchronization
63020:M 23 Aug 2023 16:31:46.275 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'de9041ea80de6
dd26eb900875af227072bf54e72', my replication IDs are '642621fae8265d57501adcb400e91572c8a4cc58' and 'dbc3411351a45a2678799cfb2300142
9a1ce3396')
63020:M 23 Aug 2023 16:31:46.275 * Starting BGSAVE for SYNC with target: disk
63020:M 23 Aug 2023 16:31:46.277 * Background saving started by pid 64458
64458:C 23 Aug 2023 16:31:46.279 * DB saved on disk
64458:C 23 Aug 2023 16:31:46.279 * RDB: 2 MB of memory used by copy-on-write
63020:M 23 Aug 2023 16:31:46.370 * Background saving terminated with success
63020:M 23 Aug 2023 16:31:46.370 * Synchronization with replica 10.201.246.17:6385 succeeded
63020:M 23 Aug 2023 16:31:46.374 * Clear FAIL state for node ea5a17aa5092e9c814a7a6371ceb72cf5bbdf3ae: master without slots is reach
able again.
63020:M 23 Aug 2023 17:31:47.049 * 1 changes in 3600 seconds. Saving...
63020:M 23 Aug 2023 17:31:47.053 * Background saving started by pid 27746
27746:C 23 Aug 2023 17:31:47.057 * DB saved on disk
27746:C 23 Aug 2023 17:31:47.058 * RDB: 2 MB of memory used by copy-on-write
63020:M 23 Aug 2023 17:31:47.153 * Background saving terminated with success