-
Type: Task
-
Resolution: Won't Do
-
Priority: 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.
- is duplicated by
-
SERVER-20371 Use clusterId for the config server check in the shard
- Closed
- is related to
-
SERVER-23096 Config server should initialize the config.version document
- Closed