[SERVER-31008] Make trying to move the primary shard to the current primary not return an error Created: 08/Sep/17 Updated: 30/Oct/23 Resolved: 12/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.12 |
| Fix Version/s: | 3.6.0-rc1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2017-10-23 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
or make it such that trying to move the primary shard of the database that is already in the requested shard not an error. |
| Comments |
| Comment by Githook User [ 12/Oct/17 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}Message: |
| Comment by Esha Maharishi (Inactive) [ 25/Sep/17 ] |
|
A better fix might be to make _configsvrMovePrimary idempotent by returning true rather than uasserting here. |