redis 3.2 protected mode

Has anybody successfully used ioredis with redis-sentinel v3.2 rc3?

I was successfully using ioredis with redis-sentinel 3.0, but on upgrading to 3.2 it silently doesn’t work, the callbacks aren’t called. It works if I directly connect to the master, bypassing the sentinel.

It appears that I’ve got my sentinel configured correctly:

127.0.0.1:26379> SENTINEL get-master-addr-by-name mymaster
1) "127.0.0.1"
2) "6379"

[fvoroshilin]

@luin, I agree with you. The redis is configured on particular interface in order to communicate with other redis. The issue was that I did not know why Sentinel did not start failover, there were not any logs in its logs. I just did not know that Sentinel should have been configured with the same option becuase there is no protected-mode setting in default config of sentinel. You know sentinel runs on 0.0.0.0 and I did not expect kind of this issue.

Initially, I removed 127.0.0.1 interface from redis configs and disabled protected-mode.

BTW, there is no bind setting in default config of sentinel as well. There is just port setting with value 26379.

Actually, my failover did not happen, after a few minutes I got this error: “-failover-abort-slave-timeout master” and I have not found a description this state. I hope to figure it out anyway or will try earlier version of redis.

[luin]

@Deathle55 protected-mode is very useful to protect your sentinel servers. You may avoid the errors by using bind directive to bind the redis/sentinel to only several specified interfaces.