-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: Cache and Eviction, History Store
-
Storage Engines, Storage Engines - Persistence
-
StorEng - 2025-04-25, SE Persistence - 2025-05-09
-
3
-
v8.1, v8.0, v7.0, v6.0
This ticket was generated after the investigation of WT-14376. We should not open the HS because of eviction during metadata recovery as it can eventually lead to data corruption.
wti_evict_app_assist_worker currently opens the history store to ensure we have cached history store cursor before performing eviction. Following this, we check whether eviction should proceed based on the eviction server existing and the cache meeting the percentage thresholds. This potentially means opening the history store unnecessarily and bailing from wti_evict_app_assist_worker because we didn't need to proceed with eviction anyway.
We should swap these checks so that we don't unnecessarily open the history store.
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
WT-14403 Remove the partial logic and rewrite __live_restore_can_service_read
-
- Closed
-
- related to
-
WT-13747 Remove obsolete page check in checkpoint skip logic
-
- Closed
-
-
-
- Closed
-