-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
With massive load and huge number of expirations the reaper might not able to handle the removal of expired entries fast enough to prevent from issues like OutOfMemory.
There should be a configuration to tweak the thread priority and maybe the number of threads handling it. Also the thread should not use the general pool which might run out of threads for this under load.
- incorporates
-
JDG-3366 Transactional cache will slow down the expiration reaper
-
- Closed
-
-
JDG-3205 Cluster Expiration should only expire primary owned entries
-
- Closed
-
- is incorporated by
-
-
- New
-
- is related to
-
-
- New
-
- links to
