Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.2, 3.5.2
Affects Version/s: None
Component/s: Replication, Testing Infrastructure
Labels:
- neweng

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.4, v3.2
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Kaloian Manassiev
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer, Kaloian Manassiev, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Dec 08 2016 04:48:28 PM UTC
Updated:: Apr 05 2017 11:41:28 AM UTC
Resolved:: Dec 17 2016 02:27:00 AM UTC
Confidence Status Last Update:: 16/Dec/16 5:03 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates