Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27339

ReplSetTest shouldn't inspect TestData directly

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v3.4, v3.2

    Description

      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

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27445 ReplSetTest throws 'TypeError: TestData is undefined' when used outside of resmoke.py

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-27117 set writeConcernMajorityJournalDefault to false in nojournal, inmem, and ephemeralForTest variants

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26747 replSetStepDown should wait for last write to commit

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              kaloian.manassiev@mongodb.com Kaloian Manassiev
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: