Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: RHDG 8.1 GA
Affects Version/s: None
Component/s: None
Labels:
- expiration

Hierarchy Progress:
0
Hierarchy Progress Bar:

0% 0%

SFDC Cases Links:
SFDC Cases Counter:

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

JDG-4421 Expiration Reaper should use multiple threads

is related to

ISPN-10677 Expiration Reaper thread should have a better name than "pool-#-thread-#"

links to

KCS article

Assignee:: Will Burns

Reporter:: Wolf Fink

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019/12/09 4:33 AM

Updated:: 2023/03/22 8:13 AM

Resolved:: 2021/03/10 12:00 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates