The jstestfuzzer provoked a WT cache full error on the in-memory engine. This should only be an issue for the in-memory engine – the durable engine should be in a panic evicting mode before this could happen. The server invariants on the error here in the JournalFlusher
We should log the warning and continue – the journal flusher runs periodically and would repeatedly log the error message, and cmds waiting for j:true would return the error message.
- is depended on by
-
SERVER-61300 Investigate memory usage of exact-topN operators for in memory storage engine in jstests/aggregation/spill_to_disk.js
-
- Closed
-
- related to
-
SERVER-79810 make JournalFlusher::waitForJournalFlush() interruptible when waiting for write concern
-
- Closed
-