1、sentinel配置
在三台设备分别进行如下sentinel的配置。
- sentinel配置文件
$ vi /etc/redis/sentinel.conf
bind 0.0.0.0
daemonize yes
port 26379
dir "/tmp"
protected-mode no
logfile "/var/log/redis-sentinel.log"
sentinel monitor mymaster 10.10.10.11 6379 2
sentinel auth-pass mymaster passwd@123
sentinel down-after-milliseconds mymaster 30000
sentinel failover-timeout mymaster 90000
sentinel parallel-syncs mymaster 1
- sentinel启动与关闭
# 启动sentinel
$ redis-sentinel /etc/redis/sentinel.conf
# 关闭sentinel
$ pkill redis-sentinel
2、配置验证
- sentinel配置验证
sentinel启动之后,由于sentinel通过master的数据交互能够学习到slave和sentinel的相关信息,因此,我们不需要在sentinel配置文件内进行slave和其他sentinel配置,这些配置sentinel启动后会自动同步到sentinel.conf配置文件。
# 启动后查看配置文件,发现配置文件被sentinel程序重写了。
cat /etc/redis/sentinel.conf
bind 0.0.0.0
daemonize yes
port 26379
dir "/tmp"
protected-mode no
logfile "/var/log/redis-sentinel.log"
sentinel myid efe679ca632193cc18b88ed7bf567290aacf807f
sentinel monitor mymaster 10.10.10.11 6379 2
sentinel failover-timeout mymaster 90000
sentinel auth-pass mymaster passwd@123
sentinel config-epoch mymaster 0
# Generated by CONFIG REWRITE # 以下是程序重写的内容
sentinel leader-epoch mymaster 0
sentinel known-slave mymaster 10.10.10.13 6379
sentinel known-slave mymaster 10.10.10.12 6379
sentinel known-sentinel mymaster 10.10.10.13 26379 4c41976bf