X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/0d1650f8a9ee2df13a11685ff0eb739305b4fe1b..2b9ce0192ef93a6b01009d381202833e10dc7e4a:/redis.conf diff --git a/redis.conf b/redis.conf index 6999dae3..18a5dd03 100644 --- a/redis.conf +++ b/redis.conf @@ -34,6 +34,7 @@ port 6379 # on a unix socket when not specified. # # unixsocket /tmp/redis.sock +# unixsocketperm 755 # Close the connection after a client is idle for N seconds (0 to disable) timeout 300 @@ -319,31 +320,48 @@ auto-aof-rewrite-min-size 64mb # your server forever. Set it to 0 or a negative value for unlimited execution. lua-time-limit 60000 -#################################### DISK STORE ############################### - -# When disk store is active Redis works as an on-disk database, where memory -# is only used as a object cache. -# -# This mode is good for datasets that are bigger than memory, and in general -# when you want to trade speed for: +################################ REDIS CLUSTER ############################### # -# - less memory used -# - immediate server restart -# - per key durability, without need for backgrond savig +# Normal Redis instances can't be part of a Redis Cluster, only nodes that are +# started as cluster nodes can. In order to start a Redis instance as a +# cluster node enable the cluster support uncommenting the following: # -# On the other hand, with disk store enabled MULTI/EXEC are no longer -# transactional from the point of view of the persistence on disk, that is, -# Redis transactions will still guarantee that commands are either processed -# all or nothing, but there is no guarantee that all the keys are flushed -# on disk in an atomic way. +# cluster-enabled yes + +# Every cluster node has a cluster configuration file. This file is not +# intended to be edited by hand. It is created and updated by Redis nodes. +# Every Redis Cluster node requires a different cluster configuration file. +# Make sure that instances running in the same system does not have +# overlapping cluster configuration file names. # -# Of course with disk store enabled Redis is not as fast as it is when -# working with just the memory back end. +# cluster-config-file nodes-6379.conf -diskstore-enabled no -diskstore-path redis.ds -cache-max-memory 0 -cache-flush-delay 0 +# In order to setup your cluster make sure to read the documentation +# available at http://redis.io web site. + +################################## SLOW LOG ################################### + +# The Redis Slow Log is a system to log queries that exceeded a specified +# execution time. The execution time does not include the I/O operations +# like talking with the client, sending the reply and so forth, +# but just the time needed to actually execute the command (this is the only +# stage of command execution where the thread is blocked and can not serve +# other requests in the meantime). +# +# You can configure the slow log with two parameters: one tells Redis +# what is the execution time, in microseconds, to exceed in order for the +# command to get logged, and the other parameter is the length of the +# slow log. When a new command is logged the oldest one is removed from the +# queue of logged commands. + +# The following time is expressed in microseconds, so 1000000 is equivalent +# to one second. Note that a negative number disables the slow log, while +# a value of zero forces the logging of every command. +slowlog-log-slower-than 10000 + +# There is no limit to this length. Just be aware that it will consume memory. +# You can reclaim memory used by the slow log with SLOWLOG RESET. +slowlog-max-len 1024 ############################### ADVANCED CONFIG ###############################