-
Enhancement
-
Resolution: Done
-
Major
-
9.4.16.Final, 10.0.0.Final
-
None
Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time.
- is cloned by
-
JDG-3205 Cluster Expiration should only expire primary owned entries
-
- Closed
-
- relates to
-
ISPN-10697 Expiration reaper should be able to handle a huge number of expired entries
-
- Resolved
-