Make expiration samples and continuation threshold configurable #568

tsee opened this Issue Jun 28, 2012 · 1 comment


None yet
1 participant

tsee commented Jun 28, 2012

The expiration logic has a fixed number of samples that it does per unit of time (10) and a fixed threshold of items that need to have been expired to continue expiring (25% == 3 given the samples). For some applications, that may not be aggressive enough.

I'd love for these to be configurable. I'm willing to implement this on top of unstable if deemed worthwhile.

tsee commented Jun 28, 2012

Obviously, this is a wishlist item, not a bug.

@Hailei Hailei pushed a commit to Hailei/redis that referenced this issue Aug 29, 2014

@marcosnils marcosnils Fix bug in JedisCluster del command. Fix #568 ddb1870
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment