diff options
author | antirez <antirez@gmail.com> | 2009-10-30 01:04:17 +0100 |
---|---|---|
committer | antirez <antirez@gmail.com> | 2009-10-30 01:04:17 +0100 |
commit | 44b38ef43259e8805b01db01ad9a1c67479c6194 (patch) | |
tree | edb0b0e1f61cfa616302d3dfe0fec8482362e44d /redis.conf | |
parent | 43e5ccdf57e2144a8a43c04c5a64e91a155a78fb (diff) | |
download | redis-44b38ef43259e8805b01db01ad9a1c67479c6194.tar.gz |
Initial implementation of append-only mode. Loading still not implemented.
Diffstat (limited to 'redis.conf')
-rw-r--r-- | redis.conf | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/redis.conf b/redis.conf index fc1e9dd90..fac5ba605 100644 --- a/redis.conf +++ b/redis.conf @@ -107,6 +107,23 @@ databases 16 # maxmemory <bytes> +############################## APPEND ONLY MODE ############################### + +# By default Redis asynchronously dumps the dataset on disk. If you can live +# with the idea that the latest records will be lost if something like a crash +# happens this is the preferred way to run Redis. If instead you care a lot +# about your data and don't want to that a single record can get lost you should +# enable the append only mode: when this mode is enabled Redis will append +# every write operation received in the file appendonly.log. This file will +# be read on startup in order to rebuild the full dataset in memory. +# +# Note that you can have both the async dumps and the append only file if you +# like (you have to comment the "save" statements above to disable the dumps). +# Still if append only mode is enabled Redis will load the data from the +# log file at startup ignoring the dump.rdb file. + +# appendonly yes + ############################### ADVANCED CONFIG ############################### # Glue small output buffers together in order to send small replies in a |