ShardingTest doesn't respect specified node options during initialization

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ClusterScalability Nov10-Nov24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current state of ShardingTest will not respect specified node options as given by passing in

      shards: [{nodes: [{ ... options ... }]}]}}
      

      This is because the way we construct the initialized shards ReplicaSetTest objects will get their nodes replaced with a number

      The simple fix is to make the code check whether we've already specified an option just like in the line above.

            Assignee:
            Kruti Shah
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: