[SERVER-23769] Add new cluster ID sanity checks for cluster with all node shard aware Created: 15/Apr/16 Updated: 06/Dec/22 Resolved: 12/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | PM-108, max-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 14/Feb/17 ] |
|
Currently we assure that a server A is receiving a command from another server X in the same cluster by checking the 'configdb' command parameter of setShardVersion against server A's knowledge of what the config connection string is: done here. Once the cluster ID check is in place, we should remove the 'configdb' config connection string check in setShardVersion. For backwards compatibility, we should accept clusterId not being present and skipping the check. |