-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Layered Tables, Verify
-
None
-
Storage Engines - Persistence
-
SE Persistence backlog
-
None
We need to investigate how we could call WT-17189 in release builds (i.e 1-in-N random checks)
If we, for example, verify 1 in 10,000 records, chosen at random, when garbage collecting ingest tables, it might give us some signal about possible issues. (TBD: What is the right frequency? Should we verify a single value, or an entire chain of values for a key chosen at random? etc.)
- has to be done after
-
WT-17189 During GC, verify the most recent update against the stable table in debug build
-
- In Progress
-