Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
As observed, FullTableCache cleanup queue consumes 4GB as events keeps getting added to queue (reached 28442228 for this case) for cleanup of evictionEntries.
There is a possibility of this due to lock used in cleanup thread, and this lock is non-fair.
As part of this, need check if evictionEntries can be optimized as used for cache eviction when cache value is null and epoch is current value transaction Id. and/or fair locking mechanism.
Attachments
Attachments
Issue Links
- links to