Redis Sentinel故障切换未按预期发生

Question

我设置了一个Redis复制和Redis Sentinel。

据我所知，一切都配置得很好。

这是主服务器上的redis-seninel.conf：

sentinel myid c975aac973e325412d2a70a5b9f6195fcb9e40e7
sentinel deny-scripts-reconfig yes
sentinel monitor redisoctcluster 10.97.7.140 6360 2
sentinel down-after-milliseconds redisoctcluster 5000

# Generated by CONFIG REWRITE
port 26379
dir "/etc/redis"
protected-mode no
sentinel failover-timeout redisoctcluster 60000
sentinel config-epoch redisoctcluster 0
sentinel leader-epoch redisoctcluster 11
sentinel known-replica redisoctcluster 10.103.19.57 6360
sentinel known-sentinel redisoctcluster 10.103.19.57 26379 fd19cf80e9b23db1501d9bfcc01aaff711a7b44b

sentinel current-epoch 11

这是从服务器上的redis-seninel.conf：

sentinel myid fd19cf80e9b23db1501d9bfcc01aaff711a7b44b
sentinel deny-scripts-reconfig yes
#bind 0.0.0.0
sentinel monitor redisoctcluster 10.97.7.140 6360 2
sentinel down-after-milliseconds redisoctcluster 5000
logfile "/var/log/redis/redis-sentinel.log"
# Generated by CONFIG REWRITE
port 26379
dir "/etc/redis"
protected-mode no
sentinel failover-timeout redisoctcluster 60000
sentinel config-epoch redisoctcluster 0
sentinel leader-epoch redisoctcluster 11
sentinel known-replica redisoctcluster 10.103.19.57 6360
sentinel known-sentinel redisoctcluster 10.97.7.140 26379 c975aac973e325412d2a70a5b9f6195fcb9e40e7

sentinel current-epoch 11

据我所知，将redis-cli用于sentinel (在主服务器和从服务器上)-一切都很好：

# redis-cli -p 26379 info sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=redisoctcluster,status=ok,address=10.97.7.140:6360,slaves=1,sentinels=2

在从服务器上运行get-master-addr-by-name，表明它知道主服务器：

# redis-cli -p 26379 sentinel get-master-addr-by-name  redisoctcluster
1) "10.97.7.140"
2) "6360"

不过，当我在主服务器上停止Redis时，我在前哨日志中看到了以下内容：

 # +odown master redisoctcluster 10.97.7.140 6360 #quorum 2/2
 # +new-epoch 10
 # +try-failover master redisoctcluster 10.97.7.140 6360
 # +vote-for-leader fd19cf80e9b23db1501d9bfcc01aaff711a7b44b 10
 # c975aac973e325412d2a70a5b9f6195fcb9e40e7 voted for fd19cf80e9b23db1501d9bfcc01aaff711a7b44b 10
 # +elected-leader master redisoctcluster 10.97.7.140 6360
 # +failover-state-select-slave master redisoctcluster 10.97.7.140 6360
 # -failover-abort-no-good-slave master redisoctcluster 10.97.7.140 6360
 # Next failover delay: I will not start a failover before Sun Nov  8 16:34:42 2020

我的配置出了什么问题，导致故障转移无法发生？

Answer 1

我不得不将redis.conf文件和redis-seninel.conf文件中的绑定参数更改为0.0.0.0才能解决这个问题:绑定0.0.0.0

然后，"sdown“通知消失，故障转移发生。