-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
ALL
This test hangs when using Biggie storage engine: jstests/replsets/awaitable_ismaster_on_nodes_with_invalid_configs.js
The new config is not propagated correctly and nodes wait indefinitely to find themselves in the config.
The test triggers these warnings in the log:
"** WARNING: This replica set node is running without journaling enabled but the "
"** writeConcernMajorityJournalDefault option to the replica set config "
"** is set to true. The writeConcernMajorityJournalDefault "
"** option to the replica set config must be set to false "
"** or w:majority write concerns will never complete."
"** In addition, this node's memory consumption may increase until all"
"** available free RAM is exhausted."
""
""
"** WARNING: This replica set node is using in-memory (ephemeral) storage with the"
"** writeConcernMajorityJournalDefault option to the replica set config "
"** set to true. The writeConcernMajorityJournalDefault option to the "
"** replica set config must be set to false "
"** or w:majority write concerns will never complete."
"** In addition, this node's memory consumption may increase until all"
"** available free RAM is exhausted."
""
writeConcernMajorityJournalDefault is supposed to be set to off:
https://github.com/mongodb/mongo/blob/1772b9a0393b55e6a280a35e8f0a1f75c014f301/buildscripts/resmokelib/testing/fixtures/replicaset.py#L186-L194
https://github.com/mongodb/mongo/blob/8f47c01aee6a78456d197b9a49da0241db081f21/src/mongo/shell/replsettest.js#L1113-L1142
But there seem to be paths where this does not happen