-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
Storage Engines
-
8
-
2024-08-06 - Withholding Tax, StorEng - 2024-09-17, 2024-09-03 Q3 Streams v1, StorEng - 2024-10-01, StorEng - 2024-10-15, StorEng - 2024-10-29
Eviction Server currently uses a hazard pointer to remember its scanning position. It has a number of negative implications:
- The page it pinned in memory and can't be evicted or split.
- If the pointer is cleared, the eviction walk can't continue.
- We run into a trouble if there are > 1000 dhandles.
Investigate the use of "soft" pointers like a key in a page or a "normalized position" of the page and implement it.
- is related to
-
WT-13790 Make a feature flag for use of "soft pointers" in eviction server
- In Code Review
-
WT-13178 Investigate performance impact of using "soft pointers" in Eviction Server
- Closed
- split from
-
WT-9121 Eviction server thread always reset the traversing point when exiting -- parts of the B-tree may never be traversed by eviction in some simple cases/
- Closed
- split to
-
WT-13375 Potential race condition use-after-free in eviction server
- Closed