From 7682548f1fd61c8035f45925fb427b80f0348997 Mon Sep 17 00:00:00 2001 From: Steffen Mueller Date: Mon, 21 May 2012 18:18:11 +0200 Subject: [PATCH] Note the expire loop config in the example config --- redis.conf | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/redis.conf b/redis.conf index 60558c008cf8..50d3c4117b0b 100644 --- a/redis.conf +++ b/redis.conf @@ -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 ###################################