node01 master:
# Replication
role:master
connected_slaves:2
slave0:ip=10.10.17.202,port=6379,state=online,offset=10592530,lag=1
slave1:ip=10.10.17.201,port=6379,state=online,offset=10592671,lag=1
master_repl_offset:10592812
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:9544237
repl_backlog_histlen:1048576
[root@node03 redis-sentinel]# cat sentinel.conf | grep -v "^#"
port 26381
protected-mode no
dir "/usr/local/bin"
logfile "/root/redis-sentinel/sentinel.log"
sentinel myid 7af3ee8048618126437b1c142c6fae6240db7f77
sentinel monitor mymaster 10.10.17.200 6379 1
sentinel down-after-milliseconds mymaster 5000
daemonize yes
sentinel failover-timeout mymaster 15000
sentinel config-epoch mymaster 96
sentinel leader-epoch mymaster 96
sentinel known-slave mymaster 10.10.17.202 6379
sentinel known-slave mymaster 10.10.17.201 6379
sentinel known-sentinel mymaster 10.10.17.201 26380 de60e451086f9d9a75a91760f5475277d5985c42
sentinel known-sentinel mymaster 10.10.17.200 26379 ba20d39f78a305a6438ca1ce38fae118fb17859e
sentinel current-epoch 96
node02:
# Replication
role:slave
master_host:10.10.17.200
master_port:6379
master_link_status:up
master_last_io_seconds_ago:1
master_sync_in_progress:0
slave_repl_offset:10790273
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
[root@node02 redis-sentinel]# cat sentinel.conf
port 26380
protected-mode no
dir "/usr/local/bin"
logfile "/root/redis-sentinel/sentinel.log"
sentinel myid de60e451086f9d9a75a91760f5475277d5985c42
sentinel monitor mymaster 10.10.17.200 6379 1
sentinel down-after-milliseconds mymaster 5000
daemonize yes
# Generated by CONFIG REWRITE
sentinel failover-timeout mymaster 15000
sentinel config-epoch mymaster 96
sentinel leader-epoch mymaster 96
sentinel known-slave mymaster 10.10.17.201 6379
sentinel known-slave mymaster 10.10.17.202 6379
sentinel known-sentinel mymaster 10.10.17.202 26381 7af3ee8048618126437b1c142c6fae6240db7f77
sentinel known-sentinel mymaster 10.10.17.200 26379 ba20d39f78a305a6438ca1ce38fae118fb17859e
sentinel current-epoch 96
node03:
# Replication
role:slave
master_host:10.10.17.200
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:136190
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
127.0.0.1:6379> exit
[root@node03 redis-sentinel]# cat sentinel.conf
port 26381
protected-mode no
dir "/usr/local/bin"
logfile "/root/redis-sentinel/sentinel.log"
sentinel myid 7af3ee8048618126437b1c142c6fae6240db7f77
sentinel monitor mymaster 10.10.17.200 6379 1
sentinel down-after-milliseconds mymaster 5000
daemonize yes
# Generated by CONFIG REWRITE
sentinel failover-timeout mymaster 15000
sentinel config-epoch mymaster 96
sentinel leader-epoch mymaster 96
sentinel known-slave mymaster 10.10.17.202 6379
sentinel known-slave mymaster 10.10.17.201 6379
sentinel known-sentinel mymaster 10.10.17.201 26380 de60e451086f9d9a75a91760f5475277d5985c42
sentinel known-sentinel mymaster 10.10.17.200 26379 ba20d39f78a305a6438ca1ce38fae118fb17859e
sentinel current-epoch 96
# sentinel monitor <master-name> <ip> <redis-port> <quorum>
告诉Sentinel来监控这个master, 认为他是O_DOWN(客观下线)状态只有当至少<quorum> sentinels agree.
请注意,无论是多少ODOWN quorum,一个哨兵需要以大多数已知的哨兵选出来进行一个failover
Slave 是自动发现的,因此你不需要指定slave.
哨兵本身会重写这个配置文件 增加slaves额外的配置信息
同时配置文件也会被重写当一个slave是提升为一个master