When running validate with {full: true}, we call WT_SESSION::verify() on all tables belonging to the collection. This will report if any keys are out-of-order. However, we have no checks to detect out-of-order keys when running {full: false}. In fact we invariant that RecordIds are returned in order, which can lead to a crash.
- related to
-
SERVER-71950 Fail and log the operation when out-of-order keys are detected in WiredTiger
- Closed
-
SERVER-72677 Full validation doesn't always report information about indexes
- Closed