diff options
Diffstat (limited to 'redis.conf')
| -rw-r--r-- | redis.conf | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/redis.conf b/redis.conf index c54dba392..7eb692a8d 100644 --- a/redis.conf +++ b/redis.conf @@ -59,7 +59,7 @@ # internet, binding to all the interfaces is dangerous and will expose the # instance to everybody on the internet. So by default we uncomment the # following bind directive, that will force Redis to listen only into -# the IPv4 lookback interface address (this means Redis will be able to +# the IPv4 loopback interface address (this means Redis will be able to # accept connections only from clients running into the same computer it # is running). # @@ -296,7 +296,9 @@ dir ./ # # 2) if slave-serve-stale-data is set to 'no' the slave will reply with # an error "SYNC with master in progress" to all the kind of commands -# but to INFO and SLAVEOF. +# but to INFO, SLAVEOF, AUTH, PING, SHUTDOWN, REPLCONF, ROLE, CONFIG, +# SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB, +# COMMAND, POST, HOST: and LATENCY. # slave-serve-stale-data yes @@ -606,7 +608,7 @@ slave-priority 100 # deletion of the object. It means that the server stops processing new commands # in order to reclaim all the memory associated with an object in a synchronous # way. If the key deleted is associated with a small object, the time needed -# in order to execute th DEL command is very small and comparable to most other +# in order to execute the DEL command is very small and comparable to most other # O(1) or O(log_N) commands in Redis. However if the key is associated with an # aggregated value containing millions of elements, the server can block for # a long time (even seconds) in order to complete the operation. @@ -621,7 +623,7 @@ slave-priority 100 # It's up to the design of the application to understand when it is a good # idea to use one or the other. However the Redis server sometimes has to # delete keys or flush the whole database as a side effect of other operations. -# Specifically Redis deletes objects independently of an user call in the +# Specifically Redis deletes objects independently of a user call in the # following scenarios: # # 1) On eviction, because of the maxmemory and maxmemory policy configurations, @@ -914,7 +916,7 @@ lua-time-limit 5000 # Docker and other containers). # # In order to make Redis Cluster working in such environments, a static -# configuration where each node known its public address is needed. The +# configuration where each node knows its public address is needed. The # following two options are used for this scope, and are: # # * cluster-announce-ip |