-
-
Save jdelStrother/9369127 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Redis configuration file example | |
#slaveof 10.12.86.71 6379 | |
daemonize yes | |
pidfile /ec/var/redis/redis_6379.pid | |
timeout 300 | |
loglevel notice | |
logfile /home/audioboo/logs/redis_6379.log | |
databases 16 | |
save 900 1 | |
save 300 10 | |
save 60 10000 | |
rdbcompression yes | |
dbfilename dump.rdb | |
dir /ec/var/redis | |
appendonly no | |
appendfsync everysec | |
activerehashing yes | |
# The client output buffer limits can be used to force disconnection of clients | |
# that are not reading data from the server fast enough for some reason (a | |
# common reason is that a Pub/Sub client can't consume messages as fast as the | |
# publisher can produce them). | |
# | |
# The limit can be set differently for the three different classes of clients: | |
# | |
# normal -> normal clients | |
# slave -> slave clients and MONITOR clients | |
# pubsub -> clients subcribed to at least one pubsub channel or pattern | |
# | |
# The syntax of every client-output-buffer-limit directive is the following: | |
# | |
# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds> | |
# | |
# A client is immediately disconnected once the hard limit is reached, or if | |
# the soft limit is reached and remains reached for the specified number of | |
# seconds (continuously). | |
# So for instance if the hard limit is 32 megabytes and the soft limit is | |
# 16 megabytes / 10 seconds, the client will get disconnected immediately | |
# if the size of the output buffers reach 32 megabytes, but will also get | |
# disconnected if the client reaches 16 megabytes and continuously overcomes | |
# the limit for 10 seconds. | |
# | |
# By default normal clients are not limited because they don't receive data | |
# without asking (in a push way), but just after a request, so only | |
# asynchronous clients may create a scenario where data is requested faster | |
# than it can read. | |
# | |
# Instead there is a default limit for pubsub and slave clients, since | |
# subscribers and slaves receive data in a push fashion. | |
# | |
# Both the hard or the soft limit can be disabled by setting them to zero. | |
client-output-buffer-limit normal 0 0 0 | |
client-output-buffer-limit slave 1gb 128mb 60 | |
client-output-buffer-limit pubsub 32mb 8mb 60 | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment