-
Enhancement
-
Resolution: Done
-
Major
-
JDG 7.3 GA
-
None
-
DataGrid Sprint #35, DataGrid Sprint #36
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.
- clones
-
ISPN-10678 Cluster Expiration Reaper should only expire primary owned entries
- Closed
- incorporates
-
ISPN-10696 Cluster Expiration reaper limits parallel expirations too much
- Closed
- is incorporated by
-
JDG-3388 Expiration Reaper thread should have a configuration to tweak priority
- Closed
- relates to
-
JDG-3209 Massive Expiration can not be handled by the reaper without backlog and cause OutOfMemory
- Closed
- links to