diff options
author | antirez <antirez@gmail.com> | 2014-09-17 11:10:09 +0200 |
---|---|---|
committer | antirez <antirez@gmail.com> | 2014-09-17 11:10:09 +0200 |
commit | c89afc8e5db6166bd8855bf48d5d7f7cc16492ad (patch) | |
tree | c8c3424ab3cd1f7997292c74899f46a4bae307ef /redis.conf | |
parent | a2c740ea931580efe2f7414661ab3c896ce8e401 (diff) | |
download | redis-c89afc8e5db6166bd8855bf48d5d7f7cc16492ad.tar.gz |
Cluster: new option to work with partial slots coverage.
Diffstat (limited to 'redis.conf')
-rw-r--r-- | redis.conf | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/redis.conf b/redis.conf index 0aa2dc9fd..e03b3aa9a 100644 --- a/redis.conf +++ b/redis.conf @@ -660,6 +660,19 @@ lua-time-limit 5000 # # cluster-migration-barrier 1 +# By default Redis Cluster nodes stop accepting queries if they detect there +# is at least an hash slot uncovered (no available node is serving it). +# This way if the cluster is partially down (for example a range of hash slots +# are no longer covered) all the cluster becomes, eventually, unavailable. +# It automatically returns available as soon as all the slots are covered again. +# +# However sometimes you want the subset of the cluster which is working, +# to continue to accept queries for the part of the key space that is still +# covered. In order to do so, just set the cluster-require-full-coverage +# option to no. +# +# cluster-require-full-coverage yes + # In order to setup your cluster make sure to read the documentation # available at http://redis.io web site. |