[SERVER-25108] test addShard and removeShard from legacy mongos during continuous config stepdown Created: 15/Jul/16 Updated: 25/Aug/16 Resolved: 25/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 17 (07/15/16), Sharding 2016-08-29 | ||||||||
| Participants: | |||||||||
| Description |
|
this case is not currently tested, but handling addShard and removeShard from a legacy mongos heavily depends on asynchronous tasks on the primary config |