In WiredTiger, we have a session verify functionality which performs validation on all the btrees inside the database. Some the validation includes, checking the ordering transaction ids, and the ordering of k/v pairs.

Aim:
Currently it is not possible to create strict timestamp ordering when calling session wt tooling verify. The reason is because WiredTiger needs to manage mixed mode timestamps and out of order timestamps, and this means that timestamps in WT isn't always in order. WT makes sure that any mixed mode timestamps and OOO timestamps, can only maintain its out of order entries when its memory and it has to be strictly in order when the entries are on-disk.
Therefore this ticket aims to only call verify when we just have re-opened the database and performed recovery when necessary. This ensures that all entries are written on disk.