Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
The hand crafted segment cache in SegmentTracker is prone to lock contentions in concurrent access scenarios. As SegmentNodeStore#merge might also end up acquiring this lock while holding the commit semaphore the situation can easily lead to many threads being blocked on the commit semaphore. The SegmentTracker cache doesn't differentiate between read and write access, which means that reader threads can block writer threads.
Attachments
Attachments
Issue Links
- depends upon
-
OAK-3095 Add eviction listener to LIRS cache
- Closed
- is blocked by
-
OAK-3095 Add eviction listener to LIRS cache
- Closed
- is depended upon by
-
OAK-3168 SegmentCache flushes Segment on update
- Closed
- is related to
-
OAK-3168 SegmentCache flushes Segment on update
- Closed
- relates to
-
OAK-3007 SegmentStore cache does not take "string" map into account
- Closed