-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Testing Infrastructure
-
Fully Compatible
-
ALL
-
v3.4, v3.2
ReplSetTest uses the TestData object provided by resmoke to determine if journaling is on and if the storage engine requires persistence. If a ReplSetTest is started by mongo --nodb, there is no TestData object. This is a problem in the following two places:
https://github.com/mongodb/mongo/blob/d55eb9d186f3039695a4d710116e79ad04536409/src/mongo/shell/replsettest.js#L623-L624
https://github.com/mongodb/mongo/blob/d55eb9d186f3039695a4d710116e79ad04536409/src/mongo/shell/replsettest.js#L295-L296
- is duplicated by
-
SERVER-27445 ReplSetTest throws 'TypeError: TestData is undefined' when used outside of resmoke.py
- Closed
- related to
-
SERVER-27117 set writeConcernMajorityJournalDefault to false in nojournal, inmem, and ephemeralForTest variants
- Closed
-
SERVER-26747 replSetStepDown should wait for last write to commit
- Closed