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

Refactor mongot setup in python test fixutre

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing

      Due to the current integration of mongot setup in python test fixture, we are forced to spawn routers (mognos binary) after the shards (mongod binary).

      As also explained in this comment this is because the mongot parameters (namely mongot port) is decided during the setup of the shard replicaset fixture.

      The goal of this ticket is to re-organize the mongot startup code so that the mongot parameters are already known when ShardedClusterFixture::setup() function is called. This allows us to spawn both mongos and mongod binaries concurrently.

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: