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

Fix how ShardingTest handles setParameters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Security 2021-04-05

      Description

       

      When adding setParameters for sharding tests like this:

      options = {
          ...,
          other: {
            mongosOptions: {
              setParameter: {
                param1: val,
                param2 ...
              }
            },
          }
        }
      st = new ShardingTest(options);

      The test runner adds an extra setParameter - migrationLockAcquisitionMaxWaitMS for the mongos which causes it to fail to start. Instead, a user has to add set parameters like this - setParameter: "param1=val", which does not allow a user to specify multiple setParameters in an intuitive way (or possibly at all). See this example for how the ShardingTest set parameter needs to be specified.

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ben.caimano Benjamin Caimano (Inactive)
              Reporter:
              shreyas.kalyan Shreyas Kalyan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: