Geek Answers Handbook

Redis Sentinel for Windows

I am successfully using Redis for Windows (2.6.8-pre2) in setting up a master slave. However, I need to provide some automatic failover options, and it seems that the watch is the most popular choice. When I run redis in sentinel mode, the sentinel connects, but he always thinks that the master is turned off. In addition, when I run the sentinel’s main team, it reports that there are 0 subordinates (not true) and that there are no other sentries (again, not true). So he seems to be connecting to the master, but not correctly.

Has anyone else seen this problem on Windows and, more importantly, has anyone successfully used sentinel in a Windows environment? Any help or direction is generally appreciated!

+4
source share
1 answer

I recommend using this:

  • 1 master node redis server 1 subordinate node redis server

  • List item 3 redis sentries with quorum 2

It is so important to have more than 3 hours to get an odd quorum. I made this configuration on Windows 7 and it works well.

Sentinel conf example:

port 20001
logfile "sentinel1.log"

sentinel monitor shard1 127.0.0.1 16379 2
sentinel down-after-milliseconds shard1 5000
sentinel failover-timeout shard1 30000
0
source

More articles:


All Articles