[SERVER-19219] Audit the new shard validation logic for addShard Created: 29/Jun/15 Updated: 31/Jul/15 Resolved: 31/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 8 08/28/15 | ||||||||
| Participants: | |||||||||
| Description |
|
The addShard commands does numerous checks to ensure that a connection string, which is being added is actually suitable to become a shard. We should make the check to also use getCmdLineOpts to ensure that we are not adding a 3.2 config server as a shard. |