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

Validate shardIdentity document of proposed shard when adding a shard that already exists

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

      After SERVER-24213 we will be returning success when running addShard for a shard that already exists. Rather than just accepting the shard name and replica set name matching an existing shard, we should also contact the proposed shard, read its shardIdentity document, and verify that the relevant information matches what we expect for the existing shard (clusterId, shardId, etc)

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: