This test was written to detect a log message at the start of the oplog application process during recovery. Since we have a bounded buffer for storing log messages for tests, the log message that we are looking for may no longer be around if the startup logs are too verbose. Instead, we can make the test more robust by checking the results at the end of the oplog application.
- is related to
-
SERVER-34941 Add testing to cover cases where timestamps cause cache pressure
- Closed
-
SERVER-32334 Update startup/rollback recovery to use new Applier interface for oplog application
- Closed
-
SERVER-50300 Log $v:2 update oplog entries from the modifier style update system
- Closed
-
SERVER-48452 Internal readers should default to reading without a timestamp
- Closed
- related to
-
SERVER-51516 fix log message search in recovery_wt_cache_full.js
- Closed