-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.7.8
-
Component/s: Testing Infrastructure
-
Storage Execution
-
ALL
-
Some replsets tests check that a
{ j: true }write on a server with --nojournal fails. The method to detect whether an engine is journaling is `StorageEngine::isDurable()'
Some engines are unconditionally durable, so they always return true for isDurable and ignore the --nojournal option. As a result the write command API won't reject writes due to
{ j: 1 }because it seems like a valid thing to do (and it is because the engine supports journaling).
If we want to keep the current semantics, we should check for the '--nojournal' option in the command line params struct instead of asking the storage engine whether or not it is durable. But I think the tests should just be fixed to accept the fact that some engines always enable journaling.
The tests that fail include:
jstests/gle/gle_sharded_wc.js
jstests/replsets/bulk_api_wc.js
jstests/replsets/batch_write_command_wc.js
- is related to
-
SERVER-15991 Command line options invalid for a storage engine should be fatal
- Closed
-
DRIVERS-190 Test against non-mmapv1 storage engine
- Closed