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

Add new cluster ID sanity checks for cluster with all node shard aware

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding

      • Whenever a mongos connects to a shard, the cluster id should match that of the mongos. This is achieved by checking the clusterId response from the isMaster response. The only exception to this rule is during the process of adding the shard.
      • Whenever a mongos or mongod connects to a config server, the cluster id should match with the current one it is a member of.
      • When a mongos starts up, it will initially have the no knowledge of the clusterId and it will get this information from the first config server it contacts. Since a mongos will need to talk to a config server before it can learn about the shards, it should use the clusterId to double check with the shards.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: