Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Sentinel: never select the slave on remote data center as master #1574

springside opened this Issue Mar 3, 2014 · 4 comments


None yet
3 participants

ghost commented Mar 3, 2014

Here is the MongoDB Geographically Distributed Replica Sets

mongo can set the remote slave with priority 0 , so new master will only be selected from slaves on local data center.

How redis do the same thing?


ghost commented Mar 3, 2014

BTW. is there any document about Redis geographically replication?

r8k commented Mar 3, 2014



HeartSaVioR commented Mar 3, 2014

@springside Hello! Did you find this configuration?

# The slave priority is an integer number published by Redis in the INFO output.
# It is used by Redis Sentinel in order to select a slave to promote into a
# master if the master is no longer working correctly.
# A slave with a low priority number is considered better for promotion, so
# for instance if there are three slaves with priority 10, 100, 25 Sentinel will
# pick the one with priority 10, that is the lowest.
# However a special priority of 0 marks the slave as not able to perform the
# role of master, so a slave with priority of 0 will never be selected by
# Redis Sentinel for promotion.
# By default the priority is 100.
slave-priority 100

ghost commented Mar 3, 2014

ok, thank you. @HeartSaVioR

@ghost ghost closed this Mar 3, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment