summaryrefslogtreecommitdiff
path: root/redis.conf
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2009-10-30 13:48:53 +0100
committerantirez <antirez@gmail.com>2009-10-30 13:48:53 +0100
commit48f0308ad327d3bf4a89c1fc1ca977b7ed6f0f96 (patch)
treeea1036f699f8f033cacebac5cf017d793e8cf18a /redis.conf
parent16f9254761332a0f939cb145529d8ce5d55262a5 (diff)
downloadredis-48f0308ad327d3bf4a89c1fc1ca977b7ed6f0f96.tar.gz
support for appendonly mode no, always, everysec
Diffstat (limited to 'redis.conf')
-rw-r--r--redis.conf17
1 files changed, 17 insertions, 0 deletions
diff --git a/redis.conf b/redis.conf
index fac5ba605..610049ef9 100644
--- a/redis.conf
+++ b/redis.conf
@@ -124,6 +124,23 @@ databases 16
# appendonly yes
+# The fsync() calls tells the Operating System to actually write data on disk
+# instead to wait for more data in the output buffer. Some OS will really flush
+# data on disk, some other OS will just try to do it ASAP.
+#
+# Redis supports three different modes:
+#
+# no: don't fsync, just let the OS flush the data when it wants. Faster.
+# always: fsync after every write to the append only log . Slow, Safest.
+# everysec: fsync only if one second passed since the last fsync. Compromise.
+#
+# The default is "no" since it's faster and anyway safer than snapshots from
+# the point of view of durability of the latest records modified.
+
+appendfsync no
+# appendfsync always
+# appendfsync everysec
+
############################### ADVANCED CONFIG ###############################
# Glue small output buffers together in order to send small replies in a