Permalink
Browse files

Note the expire loop config in the example config

  • Loading branch information...
1 parent 6da6d01 commit 7682548f1fd61c8035f45925fb427b80f0348997 @tsee committed May 21, 2012
Showing with 20 additions and 2 deletions.
  1. +20 −2 redis.conf
View
@@ -548,10 +548,28 @@ client-output-buffer-limit pubsub 32mb 8mb 60
expiry-zmq-endpoints tcp://localhost:9998
expiry-zmq-endpoints tcp://localhost:9999
#
-# See the high-water-mark documetation of 0MQ for what the HWM does.
+# See the high-water-mark documentation of 0MQ for what the HWM does on a
+# PUSH socket.
#
#expiry-zmq-hwm 0
-
+#
+# The following settings control the multiple-expiration functionality
+# of the expire hooks for hash type values.
+# In a nutshell, if expiry-zmq-hash-max-expire-cycles is set to an integer
+# > 0, then a key/value pair that's expiring will be re-inserted into the
+# redis database after sending the expiration message. In addition to
+# reinsertion, a counter "_expire_cycles" within the hash value will be
+# incremented. When that counter hits the value of
+# expiry-zmq-hash-max-expire-cycles, then the key/value will be dropped.
+#
+# The mechanism also resets the expiration time to however many
+# milliseconds are specified with "expiry-zmq-hash-delay" PLUS
+# a random number of ms between 0 and "expiry-zmq-hash-delay-jitter".
+# (Both default to 10000ms=10s.)
+#
+#expiry-zmq-hash-max-expire-cycles 0
+#expiry-zmq-hash-delay 10000
+#expiry-zmq-hash-delay-jitter 10000
################################## INCLUDES ###################################

0 comments on commit 7682548

Please sign in to comment.