This release is unrelated to the previous ones and fixes wrong behavior when non-recommended max-memory policy is used in Redis, such as volatile-* one. I still don’t recommend to use other than noeviction policies, but at least the following case is handled better.

  • Fixed – Don’t create orphaned jobs under high memory pressure in Redis with “volatile-*” max-memory policies.