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

resmoke accepts multiple "mongodSetParameters" options but only uses the last one

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.7.0, 4.4.5, 4.0.25, 4.2.15
    • None
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • STM 2020-08-10
    • 50
    • 2

    Description

      For example: 

      resmoke --suite=core --mongodSetParameters='{enableIndexBuildCommitQuorum: false}' --mongodSetParameters='{logComponentVerbosity: {command: 2'}}

      Will override the first argument and only apply the second:

      // resmoke.py
      [MongoDFixture:job0] {"t":{"$date":"2020-04-13T14:13:05.638-04:00"},"s":"I", "c":"CONTROL", "id":21951,  "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"port":20000},"replication":{"enableMajorityReadConcern":true},
      "setParameter":... "logComponentVerbosity":"{'command': 2}", ...,
      "storage":{"dbPath":"/data/db/job0/resmoke"}}}} 

      This causes problems in testing because the "majority read concern off" suite enables custom setParameters but runs suites like the rollback_fuzzer that enables its own setParameters.

      The effect is that the builder's "mongodSetParameters" overrides those of the test suite.

      Also revert the changes in SERVER-47510

      Attachments

        Issue Links

          Activity

            People

              daniel.gottlieb@mongodb.com Daniel Gottlieb
              louis.williams@mongodb.com Louis Williams
              Votes:
              3 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: