

背景

现在对3个节点的sentinel进行配置。sentinel的配置文件在redis的安装目录中已经存在,只需要复制到指定的位置即可。
sentinel是独立进程,有对应的脚本来执行。
基于之前的redis 一主二从的架构,我们继续启动3个sentinel进程。
哨兵模式的架构图如下:

protected-mode noport 26379
daemonize yespidfile "/var/run/redis-sentinel_26379.pid"logfile "/usr/local/redis-6.2.14/logs/redis-sentinel_26379.log"dir "/private/tmp"
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel announce-hostnames no# Generated by CONFIG REWRITEuser default on nopass ~* &* +@allsentinel myid c384816840b671b2f194ebd417458c6bbd08230csentinel config-epoch mymaster 0sentinel leader-epoch mymaster 0sentinel current-epoch 0sentinel known-replica mymaster 127.0.0.1 6381sentinel known-replica mymaster 127.0.0.1 6380sentinel known-sentinel mymaster 127.0.0.1 26381 789f7ad2247aa6104665ced751c1956e87ec175bsentinel known-sentinel mymaster 127.0.0.1 26380 e43e1bc4459a782d2049f8ab1dd8938e17c90ced启动sentinel,查看哨兵信息:

protected-mode noport 26380
daemonize yespidfile "/var/run/redis-sentinel_26379.pid"logfile "/usr/local/redis-6.2.14/logs/redis-sentinel_26379.log"dir "/private/tmp"
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel announce-hostnames no# Generated by CONFIG REWRITEuser default on nopass ~* &* +@allsentinel myid c384816840b671b2f194ebd417458c6bbd08230csentinel config-epoch mymaster 0sentinel leader-epoch mymaster 0sentinel current-epoch 0sentinel known-replica mymaster 127.0.0.1 6381sentinel known-replica mymaster 127.0.0.1 6380sentinel known-sentinel mymaster 127.0.0.1 26381 789f7ad2247aa6104665ced751c1956e87ec175bsentinel known-sentinel mymaster 127.0.0.1 26380 e43e1bc4459a782d2049f8ab1dd8938e17c90ced启动sentinel,查看哨兵信息:

protected-mode noport 26381
daemonize yespidfile "/var/run/redis-sentinel_26379.pid"logfile "/usr/local/redis-6.2.14/logs/redis-sentinel_26379.log"dir "/private/tmp"
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel announce-hostnames no# Generated by CONFIG REWRITEuser default on nopass ~* &* +@allsentinel myid c384816840b671b2f194ebd417458c6bbd08230csentinel config-epoch mymaster 0sentinel leader-epoch mymaster 0sentinel current-epoch 0sentinel known-replica mymaster 127.0.0.1 6381sentinel known-replica mymaster 127.0.0.1 6380sentinel known-sentinel mymaster 127.0.0.1 26381 789f7ad2247aa6104665ced751c1956e87ec175bsentinel known-sentinel mymaster 127.0.0.1 26380 e43e1bc4459a782d2049f8ab1dd8938e17c90ced启动sentinel,查看哨兵信息:




06 Sep 2024 15:49:18.869:开始断开和Master进程的连接,接着持续报错说复制失败,不断地重试
(中间有30s的重试)
06 Sep 2024 15:49:49.205 * MASTER MODE enabled,即6380实例被sentinel选举为Master节点


06 Sep 2024 15:49:18.870 # Error condition on socket for SYNC: Connection refused开始断开和Master进程的连接,接着持续报错说复制失败,不断地重试
(中间有30s的重试)
06 Sep 2024 15:49:49.262 * REPLICAOF 127.0.0.1:6380 enabled ,即6380实例被sentinel选举为Master节点后,6381实例也接受现实,开始从6380实例进行数据同步
让我们进入到之前配置好的文件夹





原创声明:本文系作者授权腾讯云开发者社区发表,未经许可,不得转载。
如有侵权,请联系 cloudcommunity@tencent.com 删除。