redis哨兵集群实战

v587博客 2021-08-24

595

点击上方蓝色“V587博客”，选择“设为星标”

后台回复”微信“获取公众号专属群聊入口

01 准备

cat redis.conf | grep -v "#" | grep -v "^$" > redis6379.conf
cat redis.conf | grep -v "#" | grep -v "^$" > redis6380.conf
cat redis.conf | grep -v "#" | grep -v "^$" > redis6381.conf
cat sentinel.conf | grep -v "#" | grep -v "^$" > redis-sentinel-26379.conf

02 主从配置

redis6379.conf

bind 192.168.112.132
protected-mode yes
port 6379
daemonize yes
loglevel notice
logfile "/root/app/env/redis-5.0.5/logs/6379.log"

redis6380.conf

bind 192.168.112.132
protected-mode yes
port 6380
daemonize yes
loglevel notice
logfile "/root/app/env/redis-5.0.5/logs/6380.log"
slaveof 192.168.112.132 6379

redis6381.conf

bind 192.168.112.132
protected-mode yes
port 6381
daemonize yes
loglevel notice
logfile "/root/app/env/redis-5.0.5/logs/6381.log"
slaveof 192.168.112.132 6379

03 哨兵配置

protected-mode yes
bind 192.168.112.132
port 26379
daemonize no
pidfile "/var/run/redis-sentinel.pid"
logfile "/root/app/env/redis-5.0.5/logs/sentinel.log"
sentinel monitor mymaster 192.168.112.132 6379 1

04 关闭启动

./bin/redis-server ./conf/redis.conf
./bin/redis-server ./conf/redis6380.conf
./bin/redis-server ./conf/redis6381.conf
./bin/redis-sentinel ./conf/sentinel.conf


pkill redis

05 测试

./bin/redis-cli -h 192.168.xx.xx -p 6379
192.168.xx.xx:6379> shutdown

06 哨兵日志

20610:X 25 Feb 2020 23:30:36.594 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
20610:X 25 Feb 2020 23:30:36.594 # Redis version=5.0.5, bits=32, commit=00000000, modified=0, pid=20610, just started
20610:X 25 Feb 2020 23:30:36.594 # Configuration loaded
20610:X 25 Feb 2020 23:30:36.596 * Increased maximum number of open files to 10032 (it was originally set to 1024).
20610:X 25 Feb 2020 23:30:36.596 * Running mode=sentinel, port=26379.
20610:X 25 Feb 2020 23:30:36.596 # WARNING: The TCP backlog setting of 511 cannot be enforced because proc/sys/net/core/somaxconn is set to the lower value of 128.
20610:X 25 Feb 2020 23:30:36.597 # Sentinel ID is f3e9a5e29f47959d898d7c8238b1f74b0200436f
20610:X 25 Feb 2020 23:30:36.597 # +monitor master mymaster 192.168.112.132 6379 quorum 1
20610:X 25 Feb 2020 23:30:36.598 * +slave slave 192.168.112.132:6380 192.168.112.132 6380 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:30:36.609 * +slave slave 192.168.112.132:6381 192.168.112.132 6381 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.551 # +sdown master mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.551 # +odown master mymaster 192.168.112.132 6379 #quorum 1/1
20610:X 25 Feb 2020 23:32:30.551 # +new-epoch 6
20610:X 25 Feb 2020 23:32:30.551 # +try-failover master mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.554 # +vote-for-leader f3e9a5e29f47959d898d7c8238b1f74b0200436f 6
20610:X 25 Feb 2020 23:32:30.554 # +elected-leader master mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.554 # +failover-state-select-slave master mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.626 # +selected-slave slave 192.168.112.132:6381 192.168.112.132 6381 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.626 * +failover-state-send-slaveof-noone slave 192.168.112.132:6381 192.168.112.132 6381 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:30.710 * +failover-state-wait-promotion slave 192.168.112.132:6381 192.168.112.132 6381 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:31.016 # +promoted-slave slave 192.168.112.132:6381 192.168.112.132 6381 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:31.016 # +failover-state-reconf-slaves master mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:31.075 * +slave-reconf-sent slave 192.168.112.132:6380 192.168.112.132 6380 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:32.069 * +slave-reconf-inprog slave 192.168.112.132:6380 192.168.112.132 6380 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:32.069 * +slave-reconf-done slave 192.168.112.132:6380 192.168.112.132 6380 @ mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:32.131 # +failover-end master mymaster 192.168.112.132 6379
20610:X 25 Feb 2020 23:32:32.131 # +switch-master mymaster 192.168.112.132 6379 192.168.112.132 6381
20610:X 25 Feb 2020 23:32:32.132 * +slave slave 192.168.112.132:6380 192.168.112.132 6380 @ mymaster 192.168.112.132 6381
20610:X 25 Feb 2020 23:32:32.132 * +slave slave 192.168.112.132:6379 192.168.112.132 6379 @ mymaster 192.168.112.132 6381
20610:X 25 Feb 2020 23:33:02.156 # +sdown slave 192.168.112.132:6379 192.168.112.132 6379 @ mymaster 192.168.112.132 6381

07 疑问

20516:X 25 Feb 2020 23:15:10.635 # +try-failover master mymaster 192.168.112.132 6379
20516:X 25 Feb 2020 23:15:10.640 # +vote-for-leader f3e9a5e29f47959d898d7c8238b1f74b0200436f 3
20516:X 25 Feb 2020 23:15:10.640 # +elected-leader master mymaster 192.168.112.132 6379
20516:X 25 Feb 2020 23:15:10.640 # +failover-state-select-slave master mymaster 192.168.112.132 6379
20516:X 25 Feb 2020 23:15:10.724 # -failover-abort-no-good-slave master mymaster 192.168.112.132 6379
20516:X 25 Feb 2020 23:15:10.780 # Next failover delay: I will not start a failover before Tue Feb 25 23:21:11 2020