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.
Obviously, this is a wishlist item, not a bug.
Fix bug in JedisCluster del command. Fix #568