2009-03-22 17:30:00 +08:00
|
|
|
# Redis configuration file example
|
|
|
|
|
|
|
|
# By default Redis does not run as a daemon. Use 'yes' if you need it.
|
|
|
|
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
|
|
|
|
daemonize no
|
|
|
|
|
2009-03-23 19:31:33 +08:00
|
|
|
# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
|
|
|
|
# You can specify a custom pid file location here.
|
|
|
|
pidfile /var/run/redis.pid
|
|
|
|
|
2009-03-22 17:30:00 +08:00
|
|
|
# Accept connections on the specified port, default is 6379
|
|
|
|
port 6379
|
|
|
|
|
|
|
|
# If you want you can bind a single interface, if the bind option is not
|
|
|
|
# specified all the interfaces will listen for connections.
|
|
|
|
#
|
|
|
|
# bind 127.0.0.1
|
|
|
|
|
2009-05-20 13:36:11 +08:00
|
|
|
# Close the connection after a client is idle for N seconds (0 to disable)
|
2009-03-22 17:30:00 +08:00
|
|
|
timeout 300
|
|
|
|
|
|
|
|
# Save the DB on disk:
|
|
|
|
#
|
|
|
|
# save <seconds> <changes>
|
|
|
|
#
|
|
|
|
# Will save the DB if both the given number of seconds and the given
|
|
|
|
# number of write operations against the DB occurred.
|
|
|
|
#
|
|
|
|
# In the example below the behaviour will be to save:
|
|
|
|
# after 900 sec (15 min) if at least 1 key changed
|
|
|
|
# after 300 sec (5 min) if at least 10 keys changed
|
|
|
|
# after 60 sec if at least 10000 keys changed
|
|
|
|
save 900 1
|
|
|
|
save 300 10
|
|
|
|
save 60 10000
|
|
|
|
|
2009-04-28 00:10:00 +08:00
|
|
|
# The filename where to dump the DB
|
|
|
|
dbfilename dump.rdb
|
|
|
|
|
2009-03-22 17:30:00 +08:00
|
|
|
# For default save/load DB in/from the working directory
|
|
|
|
# Note that you must specify a directory not a file name.
|
|
|
|
dir ./
|
|
|
|
|
|
|
|
# Set server verbosity to 'debug'
|
|
|
|
# it can be one of:
|
|
|
|
# debug (a lot of information, useful for development/testing)
|
|
|
|
# notice (moderately verbose, what you want in production probably)
|
|
|
|
# warning (only very important / critical messages are logged)
|
|
|
|
loglevel debug
|
|
|
|
|
|
|
|
# Specify the log file name. Also 'stdout' can be used to force
|
|
|
|
# the demon to log on the standard output. Note that if you use standard
|
|
|
|
# output for logging but daemonize, logs will be sent to /dev/null
|
|
|
|
logfile stdout
|
|
|
|
|
2009-04-28 00:10:00 +08:00
|
|
|
# Set the number of databases. The default database is DB 0, you can select
|
|
|
|
# a different one on a per-connection basis using SELECT <dbid> where
|
|
|
|
# dbid is a number between 0 and 'databases'-1
|
2009-03-22 17:30:00 +08:00
|
|
|
databases 16
|
|
|
|
|
|
|
|
################################# REPLICATION #################################
|
|
|
|
|
|
|
|
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
|
|
|
|
# another Redis server. Note that the configuration is local to the slave
|
|
|
|
# so for example it is possible to configure the slave to save the DB with a
|
|
|
|
# different interval, or to listen to another port, and so on.
|
|
|
|
|
|
|
|
# slaveof <masterip> <masterport>
|
|
|
|
|
2009-03-27 00:23:51 +08:00
|
|
|
################################## SECURITY ###################################
|
|
|
|
|
|
|
|
# Require clients to issue AUTH <PASSWORD> before processing any other
|
|
|
|
# commands. This might be useful in environments in which you do not trust
|
|
|
|
# others with access to the host running redis-server.
|
|
|
|
#
|
|
|
|
# This should stay commented out for backward compatibility and because most
|
|
|
|
# people do not need auth (e.g. they run their own servers).
|
|
|
|
|
2009-04-08 19:46:26 +08:00
|
|
|
# requirepass foobared
|
2009-03-27 00:23:51 +08:00
|
|
|
|
2009-05-26 05:29:18 +08:00
|
|
|
################################### LIMITS ####################################
|
|
|
|
|
|
|
|
# Set the max number of connected clients at the same time. By default there
|
|
|
|
# is no limit, and it's up to the number of file descriptors the Redis process
|
|
|
|
# is able to open. The special value '0' means no limts.
|
|
|
|
# Once the limit is reached Redis will close all the new connections sending
|
|
|
|
# an error 'max number of clients reached'.
|
|
|
|
|
|
|
|
# maxclients 128
|
|
|
|
|
2009-05-28 04:53:20 +08:00
|
|
|
# Don't use more memory than the specified amount of bytes.
|
|
|
|
# When the memory limit is reached Redis will try to remove keys with an
|
|
|
|
# EXPIRE set. It will try to start freeing keys that are going to expire
|
|
|
|
# in little time and preserve keys with a longer time to live.
|
|
|
|
# Redis will also try to remove objects from free lists if possible.
|
|
|
|
#
|
|
|
|
# If all this fails, Redis will start to reply with errors to commands
|
|
|
|
# that will use more memory, like SET, LPUSH, and so on, and will continue
|
|
|
|
# to reply to most read-only commands like GET.
|
|
|
|
|
|
|
|
# maxmemory <bytes>
|
|
|
|
|
2009-03-22 17:30:00 +08:00
|
|
|
############################### ADVANCED CONFIG ###############################
|
|
|
|
|
|
|
|
# Glue small output buffers together in order to send small replies in a
|
|
|
|
# single TCP packet. Uses a bit more CPU but most of the times it is a win
|
|
|
|
# in terms of number of queries per second. Use 'yes' if unsure.
|
|
|
|
glueoutputbuf yes
|
2009-03-26 04:00:48 +08:00
|
|
|
|
|
|
|
# Use object sharing. Can save a lot of memory if you have many common
|
|
|
|
# string in your dataset, but performs lookups against the shared objects
|
|
|
|
# pool so it uses more CPU and can be a bit slower. Usually it's a good
|
|
|
|
# idea.
|
|
|
|
shareobjects no
|