Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
Repl 2019-04-22, Repl 2019-05-06
Description
In the absence of transactions, we don't have testing that secondaries roll over their oplogs when they exceed oplogSize.
This is specifically to test that work in SERVER-36494 did not prevent storage engines that do not support transactions from truncating their oplogs when transactions are not in use (ex: inMemory).
This can likely be built on top of initial_sync_oplog_rollover.js or the tests added in SERVER-36494.
Attachments
Issue Links
- depends on
-
SERVER-36494 Prevent oplog truncation of oplog entries needed for startup recovery
-
- Closed
-