-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
-
(copied to CRM)
-
13
-
Joker - StorEng - 2023-10-17, Asparagus-StorEng - 2023-10-31, c(3x10^8)-StorEng - 2023-11-14, 2024-02-20_A_near-death_puffin, 2024-03-05 - Claronald, 2024-03-19 - PacificOcean
This ticket aims to investigate and (if exists) address the issue of pages with many updates not being queued in the eviction process. Despite reaching target trigger levels, the eviction server fails to populate the eviction queue with these pages, resulting in performance degradation and application thread stalls. See the related help tickets.
Goals:
- Investigate and replicate a scenario where clean and dirty pages are evicted, but the eviction server fails to queue pages with many updates.
- Determine the underlying reason behind the eviction server's inability to queue these pages.
Outcome:
By investigating and addressing the eviction server's inability to queue pages with many updates, we aim to optimize the eviction process, prevent latency increase, and eliminate application thread stalls. This investigation (hopefully) will lead to stability in scenarios involving high update activity.
- is fixed by
-
WT-12708 Evaluation/Revision of eviction random traversal
- Closed
- is related to
-
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
-
WT-12608 Evaluation/Revision of tree-skipping logic in eviction
- Closed
-
WT-12402 Add stats to track when eviction server skips walking a tree
- Closed
-
WT-12418 Assert if the aggressive score reaches 100 but we cannot queue pages for eviction for some time
- Closed
- related to
-
WT-11368 Understanding eviction in an application that has a large number of updates
- Closed
-
WT-11774 Add diagnostic stat to investigate eviction server's inability to queue pages
- Closed
- links to