WT-10779 added back a long-dormant feature to perform per-key checks that the content in the data store and history store makes sense when considered together.
Unfortunately, the timing of this intersected badly with a Mongo-level initiative to make verification faster. While the checks are valuable, we need finer-grained control over when they run.
The approach of this ticket is to add a verify config option that will enable users to turn off this more expensive checking. It should default to on, to ensure test coverage isn't reduced on the WT side, and so that it's very clear where MongoDB is opting out of these checks.
- is related to
-
WT-10779 Enable the function __verify_key_hs
-
- Closed
-
-
-
- Closed
-
- related to
-
WT-17978 90.79% decrease in Blocks read in Variant amazon2023-perf-tests-arm64 for Task prefetch-off-verify in Test microbenchmark_prefetch_off_verify.py
-
- In Code Review
-