配置哨兵监控Redis运行情况

redis哨兵模式

当主机发生故障时从从机中自动选出一个替代主机

1.在安装目录下创建sentinel.conf文件(哨兵配置文件)添加内容格式:sentinel monitor myMonitor 127.0.0.1 6379 1

• myMonitor ：监控主数据的名称，自定义即可，可以使用大小写字母和“.-_”符号
• 127.0.0.1：监控的主数据库的IP
• 6379：监控的主数据库的端口
• 1：最低通过票数

2.启动哨兵进入哨兵配置文件所在目录:redis-server sentinel.conf --sentinel

3.启动主机和从机

[17204] 24 Dec 15:17:09.291 # +monitor master myMonitor 127.0.0.1 6379 quorum 1
[17204] 24 Dec 15:19:10.766 * +slave slave 127.0.0.1:6380 127.0.0.1 6380 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:19:40.893 * +slave slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379

可以看到哨兵已经把master和slave都监控了。 

4、测试哨兵

[17204] 24 Dec 15:25:02.822 # +sdown slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:29:49.902 * +reboot slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:29:49.991 # -sdown slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:29:59.990 * +convert-to-slave slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379

 ①将6381的slave进行shutdown，哨兵将监控到状态。然后将6381(net start redis6381)重启服务，查看哨兵控制台，②已经进行恢复 

4.设置主机故障（将master shutdown，查看哨兵后台打印信息）

 

[17204] 24 Dec 15:36:01.641 # +sdown master myMonitor 127.0.0.1 6379  #说明master服务已经宕机
[17204] 24 Dec 15:36:02.734 # +odown master myMonitor 127.0.0.1 6379 #quorum 1/1
[17204] 24 Dec 15:36:02.741 # +new-epoch 1
[17204] 24 Dec 15:36:02.742 # +try-failover master myMonitor 127.0.0.1 6379 #开始恢复
[17204] 24 Dec 15:36:02.752 # +vote-for-leader 088e5f4aacc7b95d30b57ae48652c59f62c17131 1 #投票选举哨兵leader，现在就一个哨兵所以leader就自己
[17204] 24 Dec 15:36:02.752 # +elected-leader master myMonitor 127.0.0.1 6379 # 选中leader
[17204] 24 Dec 15:36:02.753 # +failover-state-select-slave master myMonitor 127.0.0.1 6379 #选择master
[17204] 24 Dec 15:36:02.807 # +selected-slave slave 127.0.0.1:6380 127.0.0.1 6380 @ myMonitor 127.0.0.1 6379  #选中127.0.0.1:6380作为切换
[17204] 24 Dec 15:36:02.807 * +failover-state-send-slaveof-noone slave 127.0.0.1:6380 127.0.0.1 6380 @ myMonitor 127.0.0.1 6379  #发送slaveof no one命令
[17204] 24 Dec 15:36:02.886 * +failover-state-wait-promotion slave 127.0.0.1:6380 127.0.0.1 6380 @ myMonitor 127.0.0.1 6379  #等待升级master
[17204] 24 Dec 15:36:05.966 # +promoted-slave slave 127.0.0.1:6380 127.0.0.1 6380 @ myMonitor 127.0.0.1 6379  #127.0.0.1:6380升级为master
[17204] 24 Dec 15:36:05.977 # +failover-state-reconf-slaves master myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:36:06.033 * +slave-reconf-sent slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:36:06.912 * +slave-reconf-inprog slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:36:16.186 * +slave-reconf-done slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6379
[17204] 24 Dec 15:36:16.249 # +failover-end master myMonitor 127.0.0.1 6379  #故障恢复完成
[17204] 24 Dec 15:36:16.249 # +switch-master myMonitor 127.0.0.1 6379 127.0.0.1 6380 #master切换（主数据库从6379转变为6380）
[17204] 24 Dec 15:36:16.252 * +slave slave 127.0.0.1:6381 127.0.0.1 6381 @ myMonitor 127.0.0.1 6380  #添加127.0.0.1 6381从机
[17204] 24 Dec 15:36:16.255 * +slave slave 127.0.0.1:6379 127.0.0.1 6379 @ myMonitor 127.0.0.1 6380  #添加127.0.0.1 6379从机
[17204] 24 Dec 15:36:46.344 # +sdown slave 127.0.0.1:6379 127.0.0.1 6379 @ myMonitor 127.0.0.1 6380  #发现127.0.0.1 6379宕机

主机：127.0.0.1 6379

从机： 127.0.0.1 6380、127.0.0.1 6381

主机127.0.0.1 6379宕机之后：

127.0.0.1 6380变为主机

从机：127.0.0.1 6381

恢复6379之后： 

[17204] 24 Dec 16:52:19.695 # -sdown slave 127.0.0.1:6379 127.0.0.1 6379 @ myMonitor 127.0.0.1 6380

6379变为从机，6380上位成功。