During recovery oplog application we don't advance the oldest timestamp. This can pin a lot of data in the cache and we can get stuck with the cache full.
- is duplicated by
-
SERVER-35191 Stuck with cache full during rollback
- Closed
-
SERVER-35339 Complete recovery failure after unclean shutdown
- Closed
- is related to
-
SERVER-34938 Secondary slowdown or hang due to content pinned in cache by single oplog batch
- Closed
-
SERVER-36495 Cache pressure issues during recovery oplog application
- Closed
- related to
-
SERVER-33191 Cache-full hangs on 3.6
- Closed
-
SERVER-35191 Stuck with cache full during rollback
- Closed
-
SERVER-36238 replica set startup fails in wt_cache_full.js, initial_sync_wt_cache_full.js, recovery_wt_cache_full.js when journaling is disabled
- Closed
-
SERVER-51430 update log message search in recovery_wt_cache_full.js to look at end of oplog application
- Closed