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

unit tests for addShard compatibility path

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding 18 (08/05/16)

      use the ConfigServerTestFixture to mock local writes to the config with ephemeralForTest, and the NetworkInterfaceMock to mock remote writes to the added shard

      major cases to test:

      • schedule an addShard task -> check that the shard receives the shardIdentity upsert over the network and the config receives the shard state update locally
      • schedule an addShard task, and make the network return error for shardIdentity upsert -> check that task is rescheduled (shard receives shardIdentity upsert over the network and config receives the shard state locally)
      • schedule two consecutive addShard tasks with the same shard info (simulate two 3.2 mongos's trying to add the same shard) -> check that only one proceeds to send network requests to upsert the shardIdentity doc

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: