Skip to content
Newer
Older
100644 560 lines (496 sloc) 23.5 KB
ed9b544 @antirez first commit
authored
1 # Redis configuration file example
2
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
3 # Note on units: when memory size is needed, it is possible to specify
7232400 @antirez new units for bytes specification
authored
4 # it in the usual form of 1k 5GB 4M and so forth:
5 #
6 # 1k => 1000 bytes
7 # 1kb => 1024 bytes
8 # 1m => 1000000 bytes
9 # 1mb => 1024*1024 bytes
10 # 1g => 1000000000 bytes
11 # 1gb => 1024*1024*1024 bytes
12 #
13 # units are case insensitive so 1GB 1Gb 1gB are all the same.
14
ed9b544 @antirez first commit
authored
15 # By default Redis does not run as a daemon. Use 'yes' if you need it.
16 # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
17 daemonize no
18
029245f @antirez clarified a few messages in redis.conf
authored
19 # When running daemonized, Redis writes a pid file in /var/run/redis.pid by
20 # default. You can specify a custom pid file location here.
ed329fc @lucsky Allow to specify the pid file from the config file.
lucsky authored
21 pidfile /var/run/redis.pid
22
a5639e7 @pietern Change initialization to allow listening on both a port and socket
pietern authored
23 # Accept connections on the specified port, default is 6379.
68d6345 @antirez If port zero is specified, Redis will not listen for TCP connections
authored
24 # If port 0 is specified Redis will not listen on a TCP socket.
ed9b544 @antirez first commit
authored
25 port 6379
26
27 # If you want you can bind a single interface, if the bind option is not
029245f @antirez clarified a few messages in redis.conf
authored
28 # specified all the interfaces will listen for incoming connections.
ed9b544 @antirez first commit
authored
29 #
30 # bind 127.0.0.1
31
5d10923 @pietern Rename variable sockpath to unixsocket
pietern authored
32 # Specify the path for the unix socket that will be used to listen for
33 # incoming connections. There is no default, so Redis will not listen
34 # on a unix socket when not specified.
a5639e7 @pietern Change initialization to allow listening on both a port and socket
pietern authored
35 #
5d10923 @pietern Rename variable sockpath to unixsocket
pietern authored
36 # unixsocket /tmp/redis.sock
8523876 @florean Added a config directive for a Unix socket mask
florean authored
37 # unixsocketperm 755
a5639e7 @pietern Change initialization to allow listening on both a port and socket
pietern authored
38
0150db3 @tmm1 Allow timeout=0 config to disable client timeouts
tmm1 authored
39 # Close the connection after a client is idle for N seconds (0 to disable)
aba4adb @antirez use timeout 0 by default, as this is a common source of problems.
authored
40 timeout 0
ed9b544 @antirez first commit
authored
41
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
42 # Set server verbosity to 'debug'
43 # it can be one of:
44 # debug (a lot of information, useful for development/testing)
38aba9a @antirez a new default redis.conf
authored
45 # verbose (many rarely useful info, but not a mess like the debug level)
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
46 # notice (moderately verbose, what you want in production probably)
47 # warning (only very important / critical messages are logged)
c6f9ee8 @antirez default log level is now notice.
authored
48 loglevel notice
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
49
50 # Specify the log file name. Also 'stdout' can be used to force
029245f @antirez clarified a few messages in redis.conf
authored
51 # Redis to log on the standard output. Note that if you use standard
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
52 # output for logging but daemonize, logs will be sent to /dev/null
53 logfile stdout
54
e1a586e @jonahharris syslog support
jonahharris authored
55 # To enable logging to the system logger, just set 'syslog-enabled' to yes,
56 # and optionally update the other syslog parameters to suit your needs.
57 # syslog-enabled no
58
59 # Specify the syslog identity.
60 # syslog-ident redis
61
62 # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
63 # syslog-facility local0
64
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
65 # Set the number of databases. The default database is DB 0, you can select
66 # a different one on a per-connection basis using SELECT <dbid> where
67 # dbid is a number between 0 and 'databases'-1
68 databases 16
69
70 ################################ SNAPSHOTTING #################################
71 #
ed9b544 @antirez first commit
authored
72 # Save the DB on disk:
73 #
74 # save <seconds> <changes>
75 #
76 # Will save the DB if both the given number of seconds and the given
77 # number of write operations against the DB occurred.
78 #
79 # In the example below the behaviour will be to save:
80 # after 900 sec (15 min) if at least 1 key changed
81 # after 300 sec (5 min) if at least 10 keys changed
82 # after 60 sec if at least 10000 keys changed
e7546c6 @antirez BGREWRITEAOF now works with swapping on
authored
83 #
84 # Note: you can disable saving at all commenting all the "save" lines.
4aac3ff @antirez It is now posible to flush all the previous saving points in redis.co…
authored
85 #
86 # It is also possible to remove all the previously configured save
87 # points by adding a save directive with a single empty string argument
88 # like in the following example:
89 #
90 # save ""
e7546c6 @antirez BGREWRITEAOF now works with swapping on
authored
91
38aba9a @antirez a new default redis.conf
authored
92 save 900 1
93 save 300 10
94 save 60 10000
ed9b544 @antirez first commit
authored
95
4d3bbf3 @antirez By default Redis refuses writes with an error if the latest BGSAVE fa…
authored
96 # By default Redis will stop accepting writes if RDB snapshots are enabled
97 # (at least one save point) and the latest background save failed.
98 # This will make the user aware (in an hard way) that data is not persisting
99 # on disk properly, otherwise chances are that no one will notice and some
100 # distater will happen.
101 #
102 # If the background saving process will start working again Redis will
103 # automatically allow writes again.
104 #
105 # However if you have setup your proper monitoring of the Redis server
106 # and persistence, you may want to disable this feature so that Redis will
107 # continue to work as usually even if there are problems with disk,
108 # permissions, and so forth.
109 stop-writes-on-bgsave-error yes
110
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
111 # Compress string objects using LZF when dump .rdb databases?
b055378 @antirez LZF compression re-enabled by default, but with INIT_HTAB set to 0 to…
authored
112 # For default that's set to 'yes' as it's almost always a win.
113 # If you want to save some CPU in the saving child set it to 'no' but
114 # the dataset will likely be bigger if you have compressible values or keys.
115 rdbcompression yes
121f70c @antirez lzf compression switched off by default now, with config file option …
authored
116
84bcd3a @antirez It is now possible to enable/disable RDB checksum computation from re…
authored
117 # Since verison 5 of RDB a CRC64 checksum is placed at the end of the file.
118 # This makes the format more resistant to corruption but there is a performance
119 # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
120 # for maximum performances.
121 #
122 # RDB files created with checksum disabled have a checksum of zero that will
123 # tell the loading code to skip the check.
124 rdbchecksum yes
125
b8b553c @antirez ability to specify a different file name for the DB
authored
126 # The filename where to dump the DB
127 dbfilename dump.rdb
128
029245f @antirez clarified a few messages in redis.conf
authored
129 # The working directory.
130 #
131 # The DB will be written inside this directory, with the filename specified
132 # above using the 'dbfilename' configuration directive.
133 #
134 # Also the Append Only File will be created inside this directory.
135 #
136 # Note that you must specify a directory here, not a file name.
ed9b544 @antirez first commit
authored
137 dir ./
138
139 ################################# REPLICATION #################################
140
141 # Master-Slave replication. Use slaveof to make a Redis instance a copy of
142 # another Redis server. Note that the configuration is local to the slave
143 # so for example it is possible to configure the slave to save the DB with a
144 # different interval, or to listen to another port, and so on.
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
authored
145 #
ed9b544 @antirez first commit
authored
146 # slaveof <masterip> <masterport>
147
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
authored
148 # If the master is password protected (using the "requirepass" configuration
149 # directive below) it is possible to tell the slave to authenticate before
150 # starting the replication synchronization process, otherwise the master will
151 # refuse the slave request.
152 #
153 # masterauth <master-password>
154
4ebfc45 @antirez config option to select if when replication link with master a slave …
authored
155 # When a slave lost the connection with the master, or when the replication
156 # is still in progress, the slave can act in two different ways:
157 #
158 # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
92a157e @jerem Fixed a typo in comments.
jerem authored
159 # still reply to client requests, possibly with out of date data, or the
4ebfc45 @antirez config option to select if when replication link with master a slave …
authored
160 # data set may just be empty if this is the first synchronization.
161 #
162 # 2) if slave-serve-stale data is set to 'no' the slave will reply with
163 # an error "SYNC with master in progress" to all the kind of commands
164 # but to INFO and SLAVEOF.
165 #
166 slave-serve-stale-data yes
167
f3fd419 @antirez Support for read-only slaves. Semantical fixes.
authored
168 # You can configure a slave instance to accept writes or not. Writing against
169 # a slave instance may be useful to store some ephemeral data (because data
170 # written on a slave will be easily deleted after resync with the master) but
ba864e0 @antirez Comments about security of slave-read-only in redis.coinf.
authored
171 # may also cause problems if clients are writing to it because of a
172 # misconfiguration.
f3fd419 @antirez Support for read-only slaves. Semantical fixes.
authored
173 #
174 # Since Redis 2.6 by default slaves are read-only.
ba864e0 @antirez Comments about security of slave-read-only in redis.coinf.
authored
175 #
176 # Note: read only slaves are not designed to be exposed to untrusted clients
177 # on the internet. It's just a protection layer against misuse of the instance.
178 # Still a read only slave exports by default all the administrative commands
179 # such as CONFIG, DEBUG, and so forth. To a limited extend you can improve
180 # security of read only slaves using 'rename-command' to shadow all the
181 # administrative / dangerous commands.
f3fd419 @antirez Support for read-only slaves. Semantical fixes.
authored
182 slave-read-only yes
183
8996bf7 @antirez 7c6da73
authored
184 # Slaves send PINGs to server in a predefined interval. It's possible to change
185 # this interval with the repl_ping_slave_period option. The default value is 10
186 # seconds.
187 #
f15e33a fixed typo in comments
Herbert G. Fischer authored
188 # repl-ping-slave-period 10
8996bf7 @antirez 7c6da73
authored
189
190 # The following option sets a timeout for both Bulk transfer I/O timeout and
191 # master data or ping response timeout. The default value is 60 seconds.
192 #
85ccd57 @antirez added more clarifications in redis.conf about ther right value to set…
authored
193 # It is important to make sure that this value is greater than the value
194 # specified for repl-ping-slave-period otherwise a timeout will be detected
195 # every time there is low traffic between the master and the slave.
196 #
f15e33a fixed typo in comments
Herbert G. Fischer authored
197 # repl-timeout 60
8996bf7 @antirez 7c6da73
authored
198
712656e @antirez Sentinel: added documentation about slave-priority in redis.conf
authored
199 # The slave priority is an integer number published by Redis in the INFO output.
200 # It is used by Redis Sentinel in order to select a slave to promote into a
201 # master if the master is no longer working correctly.
202 #
203 # A slave with a low priority number is considered better for promotion, so
204 # for instance if there are three slaves with priority 10, 100, 25 Sentinel will
205 # pick the one wtih priority 10, that is the lowest.
206 #
207 # However a special priority of 0 marks the slave as not able to perform the
208 # role of master, so a slave with priority of 0 will never be selected by
209 # Redis Sentinel for promotion.
210 #
211 # By default the priority is 100.
212 slave-priority 100
213
f2aa84b @antirez Lua client added thanks to Daniele Alessandri
authored
214 ################################## SECURITY ###################################
215
216 # Require clients to issue AUTH <PASSWORD> before processing any other
217 # commands. This might be useful in environments in which you do not trust
218 # others with access to the host running redis-server.
219 #
220 # This should stay commented out for backward compatibility and because most
221 # people do not need auth (e.g. they run their own servers).
1b67773 @antirez CONFIG now can change appendfsync policy at run time
authored
222 #
223 # Warning: since Redis is pretty fast an outside user can try up to
224 # 150k passwords per second against a good box. This means that you should
225 # use a very strong password otherwise it will be very easy to break.
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
authored
226 #
290deb8 @antirez TODO changes, minor change to default redis.conf
authored
227 # requirepass foobared
f2aa84b @antirez Lua client added thanks to Daniele Alessandri
authored
228
8d3e063 @antirez added support for command renaming/suppression in redis.conf
authored
229 # Command renaming.
230 #
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
231 # It is possible to change the name of dangerous commands in a shared
8d3e063 @antirez added support for command renaming/suppression in redis.conf
authored
232 # environment. For instance the CONFIG command may be renamed into something
233 # of hard to guess so that it will be still available for internal-use
234 # tools but not available for general clients.
235 #
236 # Example:
237 #
238 # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
239 #
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
240 # It is also possible to completely kill a command renaming it into
8d3e063 @antirez added support for command renaming/suppression in redis.conf
authored
241 # an empty string:
242 #
243 # rename-command CONFIG ""
244
285add5 @antirez maxclients implemented, see redis.conf for details
authored
245 ################################### LIMITS ####################################
246
58732c2 @antirez maxclients configuration is now implemented dealing with the actual p…
authored
247 # Set the max number of connected clients at the same time. By default
248 # this limit is set to 10000 clients, however if the Redis server is not
249 # able ot configure the process file limit to allow for the specified limit
250 # the max number of allowed clients is set to the current file limit
251 # minus 32 (as Redis reserves a few file descriptors for internal uses).
252 #
285add5 @antirez maxclients implemented, see redis.conf for details
authored
253 # Once the limit is reached Redis will close all the new connections sending
254 # an error 'max number of clients reached'.
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
authored
255 #
58732c2 @antirez maxclients configuration is now implemented dealing with the actual p…
authored
256 # maxclients 10000
285add5 @antirez maxclients implemented, see redis.conf for details
authored
257
3fd78bc @antirez maxmemory implemented
authored
258 # Don't use more memory than the specified amount of bytes.
cebb7b9 @antirez redis.conf updated with new maxmemory semantics
authored
259 # When the memory limit is reached Redis will try to remove keys
260 # accordingly to the eviction policy selected (see maxmemmory-policy).
261 #
262 # If Redis can't remove keys according to the policy, or if the policy is
263 # set to 'noeviction', Redis will start to reply with errors to commands
264 # that would use more memory, like SET, LPUSH, and so on, and will continue
265 # to reply to read-only commands like GET.
266 #
267 # This option is usually useful when using Redis as an LRU cache, or to set
268 # an hard memory limit for an instance (using the 'noeviction' policy).
269 #
270 # WARNING: If you have slaves attached to an instance with maxmemory on,
271 # the size of the output buffers needed to feed the slaves are subtracted
272 # from the used memory count, so that network problems / resyncs will
273 # not trigger a loop where keys are evicted, and in turn the output
274 # buffer of slaves is full with DELs of keys evicted triggering the deletion
275 # of more keys, and so forth until the database is completely emptied.
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
authored
276 #
f9ef912 @antirez more practical maxmemory+slaves hint in redis.conf
authored
277 # In short... if you have slaves attached it is suggested that you set a lower
278 # limit for maxmemory so that there is some free RAM on the system for slave
279 # output buffers (but this is not needed if the policy is 'noeviction').
280 #
3fd78bc @antirez maxmemory implemented
authored
281 # maxmemory <bytes>
282
165346c @antirez implemented different algorithms for maxmemory
authored
283 # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
284 # is reached? You can select among five behavior:
285 #
286 # volatile-lru -> remove the key with an expire set using an LRU algorithm
287 # allkeys-lru -> remove any key accordingly to the LRU algorithm
288 # volatile-random -> remove a random key with an expire set
96e9f8d fix typo of redis.conf
quiver authored
289 # allkeys-random -> remove a random key, any key
165346c @antirez implemented different algorithms for maxmemory
authored
290 # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
5402c42 @antirez added noeviction policy to redis maxmemory. ZSCORE removed from the l…
authored
291 # noeviction -> don't expire at all, just return an error on write operations
292 #
293 # Note: with all the kind of policies, Redis will return an error on write
294 # operations, when there are not suitable keys for eviction.
295 #
296 # At the date of writing this commands are: set setnx setex append
297 # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
298 # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
299 # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
300 # getset mset msetnx exec sort
301 #
302 # The default is:
165346c @antirez implemented different algorithms for maxmemory
authored
303 #
304 # maxmemory-policy volatile-lru
305
306 # LRU and minimal TTL algorithms are not precise algorithms but approximated
307 # algorithms (in order to save memory), so you can select as well the sample
308 # size to check. For instance for default Redis will check three keys and
309 # pick the one that was used less recently, you can change the sample size
310 # using the following configuration directive.
311 #
a368792 @antirez maxmemory-samples implemented in CONFIG command and configuration file
authored
312 # maxmemory-samples 3
165346c @antirez implemented different algorithms for maxmemory
authored
313
44b38ef @antirez Initial implementation of append-only mode. Loading still not impleme…
authored
314 ############################## APPEND ONLY MODE ###############################
315
60e2e5b @antirez redis.conf AOF section comments improved.
authored
316 # By default Redis asynchronously dumps the dataset on disk. This mode is
317 # good enough in many applications, but an issue with the Redis process or
318 # a power outage may result into a few minutes of writes lost (depending on
319 # the configured save points).
320 #
321 # The Append Only File is an alternative persistence mode that provides
322 # much better durability. For instance using the default data fsync policy
323 # (see later in the config file) Redis can lose just one second of writes in a
324 # dramatic event like a server power outage, or a single write if something
325 # wrong with the Redis process itself happens, but the operating system is
326 # still running correctly.
327 #
328 # AOF and RDB persistence can be enabled at the same time without problems.
329 # If the AOF is enabled on startup Redis will load the AOF, that is the file
330 # with the better durability guarantees.
331 #
332 # Please check http://redis.io/topics/persistence for more information.
44b38ef @antirez Initial implementation of append-only mode. Loading still not impleme…
authored
333
4e141d5 @antirez append only mode is now able to translate EXPIRE into EXPIREAT transp…
authored
334 appendonly no
44b38ef @antirez Initial implementation of append-only mode. Loading still not impleme…
authored
335
f3b5241 @pietern make append only filename configurable
pietern authored
336 # The name of the append only file (default: "appendonly.aof")
337 # appendfilename appendonly.aof
338
4e141d5 @antirez append only mode is now able to translate EXPIRE into EXPIREAT transp…
authored
339 # The fsync() call tells the Operating System to actually write data on disk
48f0308 @antirez support for appendonly mode no, always, everysec
authored
340 # instead to wait for more data in the output buffer. Some OS will really flush
341 # data on disk, some other OS will just try to do it ASAP.
342 #
343 # Redis supports three different modes:
344 #
345 # no: don't fsync, just let the OS flush the data when it wants. Faster.
346 # always: fsync after every write to the append only log . Slow, Safest.
60e2e5b @antirez redis.conf AOF section comments improved.
authored
347 # everysec: fsync only one time every second. Compromise.
48f0308 @antirez support for appendonly mode no, always, everysec
authored
348 #
6766f45 @antirez multi bulk requests in redis-benchmark, default fsync policy changed …
authored
349 # The default is "everysec" that's usually the right compromise between
350 # speed and data safety. It's up to you to understand if you can relax this to
ce6628d @diegok Fixed a config docs typo.
diegok authored
351 # "no" that will let the operating system flush the output buffer when
6766f45 @antirez multi bulk requests in redis-benchmark, default fsync policy changed …
authored
352 # it wants, for better performances (but if you can live with the idea of
353 # some data loss consider the default persistence mode that's snapshotting),
354 # or on the contrary, use "always" that's very slow but a bit safer than
355 # everysec.
356 #
60e2e5b @antirez redis.conf AOF section comments improved.
authored
357 # More details please check the following article:
358 # http://antirez.com/post/redis-persistence-demystified.html
359 #
6766f45 @antirez multi bulk requests in redis-benchmark, default fsync policy changed …
authored
360 # If unsure, use "everysec".
361
362 # appendfsync always
363 appendfsync everysec
4e141d5 @antirez append only mode is now able to translate EXPIRE into EXPIREAT transp…
authored
364 # appendfsync no
48f0308 @antirez support for appendonly mode no, always, everysec
authored
365
d5d23da @antirez redis.conf new features the new option, a minor typo preventing the c…
authored
366 # When the AOF fsync policy is set to always or everysec, and a background
367 # saving process (a background save or AOF log background rewriting) is
368 # performing a lot of I/O against the disk, in some Linux configurations
369 # Redis may block too long on the fsync() call. Note that there is no fix for
370 # this currently, as even performing fsync in a different thread will block
371 # our synchronous write(2) call.
372 #
373 # In order to mitigate this problem it's possible to use the following option
374 # that will prevent fsync() from being called in the main process while a
375 # BGSAVE or BGREWRITEAOF is in progress.
376 #
377 # This means that while another child is saving the durability of Redis is
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
378 # the same as "appendfsync none", that in practical terms means that it is
d5d23da @antirez redis.conf new features the new option, a minor typo preventing the c…
authored
379 # possible to lost up to 30 seconds of log in the worst scenario (with the
380 # default Linux settings).
381 #
382 # If you have latency problems turn this to "yes". Otherwise leave it as
383 # "no" that is the safest pick from the point of view of durability.
384 no-appendfsync-on-rewrite no
385
b333e23 @antirez automatic AOF rewrite first implementation. Still to be tested.
authored
386 # Automatic rewrite of the append only file.
387 # Redis is able to automatically rewrite the log file implicitly calling
388 # BGREWRITEAOF when the AOF log size will growth by the specified percentage.
389 #
390 # This is how it works: Redis remembers the size of the AOF file after the
391 # latest rewrite (or if no rewrite happened since the restart, the size of
392 # the AOF at startup is used).
393 #
394 # This base size is compared to the current size. If the current size is
395 # bigger than the specified percentage, the rewrite is triggered. Also
396 # you need to specify a minimal size for the AOF file to be rewritten, this
397 # is useful to avoid rewriting the AOF file even if the percentage increase
398 # is reached but it is still pretty small.
399 #
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
400 # Specify a percentage of zero in order to disable the automatic AOF
b333e23 @antirez automatic AOF rewrite first implementation. Still to be tested.
authored
401 # rewrite feature.
402
403 auto-aof-rewrite-percentage 100
404 auto-aof-rewrite-min-size 64mb
405
eeffcf3 @antirez Lua scripts max execution time
authored
406 ################################ LUA SCRIPTING ###############################
407
408 # Max execution time of a Lua script in milliseconds.
115e3ff @antirez If a Lua script executes for more time than the max time specified in…
authored
409 #
410 # If the maximum execution time is reached Redis will log that a script is
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
411 # still in execution after the maximum allowed time and will start to
115e3ff @antirez If a Lua script executes for more time than the max time specified in…
authored
412 # reply to queries with an error.
413 #
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
414 # When a long running script exceed the maximum execution time only the
0b14e44 @antirez redis.conf updated to reflect the new scripting timeout semantics.
authored
415 # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
416 # used to stop a script that did not yet called write commands. The second
417 # is the only way to shut down the server in the case a write commands was
418 # already issue by the script but the user don't want to wait for the natural
419 # termination of the script.
115e3ff @antirez If a Lua script executes for more time than the max time specified in…
authored
420 #
421 # Set it to 0 or a negative value for unlimited execution without warnings.
422 lua-time-limit 5000
eeffcf3 @antirez Lua scripts max execution time
authored
423
07c152a @antirez cluster config file entries added to the example configuration file
authored
424 ################################ REDIS CLUSTER ###############################
425 #
426 # Normal Redis instances can't be part of a Redis Cluster, only nodes that are
427 # started as cluster nodes can. In order to start a Redis instance as a
428 # cluster node enable the cluster support uncommenting the following:
429 #
430 # cluster-enabled yes
431
432 # Every cluster node has a cluster configuration file. This file is not
433 # intended to be edited by hand. It is created and updated by Redis nodes.
434 # Every Redis Cluster node requires a different cluster configuration file.
435 # Make sure that instances running in the same system does not have
436 # overlapping cluster configuration file names.
437 #
438 # cluster-config-file nodes-6379.conf
439
440 # In order to setup your cluster make sure to read the documentation
441 # available at http://redis.io web site.
442
35a6044 @antirez slow log configuration implemented
authored
443 ################################## SLOW LOG ###################################
444
445 # The Redis Slow Log is a system to log queries that exceeded a specified
446 # execution time. The execution time does not include the I/O operations
447 # like talking with the client, sending the reply and so forth,
448 # but just the time needed to actually execute the command (this is the only
449 # stage of command execution where the thread is blocked and can not serve
450 # other requests in the meantime).
451 #
452 # You can configure the slow log with two parameters: one tells Redis
453 # what is the execution time, in microseconds, to exceed in order for the
454 # command to get logged, and the other parameter is the length of the
455 # slow log. When a new command is logged the oldest one is removed from the
456 # queue of logged commands.
457
de32c37 @antirez More redis.conf self-documentation. Now even queries that took exactl…
authored
458 # The following time is expressed in microseconds, so 1000000 is equivalent
459 # to one second. Note that a negative number disables the slow log, while
460 # a value of zero forces the logging of every command.
35a6044 @antirez slow log configuration implemented
authored
461 slowlog-log-slower-than 10000
de32c37 @antirez More redis.conf self-documentation. Now even queries that took exactl…
authored
462
463 # There is no limit to this length. Just be aware that it will consume memory.
464 # You can reclaim memory used by the slow log with SLOWLOG RESET.
d3701d2 @antirez Limit memory used by big SLOWLOG entries.
authored
465 slowlog-max-len 128
35a6044 @antirez slow log configuration implemented
authored
466
ed9b544 @antirez first commit
authored
467 ############################### ADVANCED CONFIG ###############################
468
d3ea4c8 @pietern Update default configuration
pietern authored
469 # Hashes are encoded using a memory efficient data structure when they have a
470 # small number of entries, and the biggest entry does not exceed a given
471 # threshold. These thresholds can be configured using the following directives.
472 hash-max-ziplist-entries 512
473 hash-max-ziplist-value 64
b3f83f1 @jzawodn support for include directive in config parser
jzawodn authored
474
6a246b1 @antirez special encoding limits redefined, and all the config options for spe…
authored
475 # Similarly to hashes, small lists are also encoded in a special way in order
476 # to save a lot of space. The special representation is only used when
477 # you are under the following limits:
478 list-max-ziplist-entries 512
479 list-max-ziplist-value 64
480
481 # Sets have a special encoding in just one case: when a set is composed
482 # of just strings that happens to be integers in radix 10 in the range
483 # of 64 bit signed integers.
484 # The following configuration setting sets the limit in the size of the
485 # set in order to use this special memory saving encoding.
486 set-max-intset-entries 512
487
3ea204e @pietern Configurable thresholds for encoded sorted sets
pietern authored
488 # Similarly to hashes and lists, sorted sets are also specially encoded in
489 # order to save a lot of space. This encoding is only used when the length and
490 # elements of a sorted set are below the following limits:
491 zset-max-ziplist-entries 128
492 zset-max-ziplist-value 64
493
8ca3e9d @antirez Active rehashing
authored
494 # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
495 # order to help rehashing the main Redis hash table (the one mapping top-level
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
496 # keys to values). The hash table implementation Redis uses (see dict.c)
8ca3e9d @antirez Active rehashing
authored
497 # performs a lazy rehashing: the more operation you run into an hash table
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
498 # that is rehashing, the more rehashing "steps" are performed, so if the
8ca3e9d @antirez Active rehashing
authored
499 # server is idle the rehashing is never complete and some more memory is used
500 # by the hash table.
501 #
502 # The default is to use this millisecond 10 times every second in order to
503 # active rehashing the main dictionaries, freeing memory when possible.
504 #
505 # If unsure:
506 # use "activerehashing no" if you have hard latency requirements and it is
507 # not a good thing in your environment that Redis can reply form time to time
508 # to queries with 2 milliseconds delay.
509 #
510 # use "activerehashing yes" if you don't have such hard requirements but
511 # want to free memory asap when possible.
512 activerehashing yes
513
c8a607f @antirez client-output-buffer-limit documented in redis.conf
authored
514 # The client output buffer limits can be used to force disconnection of clients
515 # that are not reading data from the server fast enough for some reason (a
516 # common reason is that a Pub/Sub client can't consume messages as fast as the
517 # publisher can produce them).
518 #
519 # The limit can be set differently for the three different classes of clients:
520 #
521 # normal -> normal clients
522 # slave -> slave clients and MONITOR clients
523 # pubsub -> clients subcribed to at least one pubsub channel or pattern
524 #
525 # The syntax of every client-output-buffer-limit directive is the following:
526 #
3cbce4f @antirez redis.conf typo fixed in the client-output-buffer-limit documentation
authored
527 # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
c8a607f @antirez client-output-buffer-limit documented in redis.conf
authored
528 #
529 # A client is immediately disconnected once the hard limit is reached, or if
530 # the soft limit is reached and remains reached for the specified number of
531 # seconds (continuously).
532 # So for instance if the hard limit is 32 megabytes and the soft limit is
533 # 16 megabytes / 10 seconds, the client will get disconnected immediately
534 # if the size of the output buffers reach 32 megabytes, but will also get
535 # disconnected if the client reaches 16 megabytes and continuously overcomes
536 # the limit for 10 seconds.
537 #
538 # By default normal clients are not limited because they don't receive data
539 # without asking (in a push way), but just after a request, so only
540 # asynchronous clients may create a scenario where data is requested faster
541 # than it can read.
542 #
543 # Instead there is a default limit for pubsub and slave clients, since
544 # subscribers and slaves receive data in a push fashion.
545 #
546 # Both the hard or the soft limit can be disabled just setting it to zero.
547 client-output-buffer-limit normal 0 0 0
548 client-output-buffer-limit slave 256mb 64mb 60
549 client-output-buffer-limit pubsub 32mb 8mb 60
550
b3f83f1 @jzawodn support for include directive in config parser
jzawodn authored
551 ################################## INCLUDES ###################################
552
553 # Include one or more other config files here. This is useful if you
57c0cf8 @kashif Fixed some typos in redis.conf.
kashif authored
554 # have a standard template that goes to all Redis server but also need
b3f83f1 @jzawodn support for include directive in config parser
jzawodn authored
555 # to customize a few per-server settings. Include files can include
556 # other files, so use this wisely.
557 #
558 # include /path/to/local.conf
559 # include /path/to/other.conf
Something went wrong with that request. Please try again.