[SERVER-30168] Make the _configsvrEnableSharding command idempotent Created: 17/Jul/17 Updated: 30/Oct/23 Resolved: 23/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.9 |
| Fix Version/s: | 3.5.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jessica Yu | Assignee: | Jessica Yu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2017-07-31 |
| Participants: |
| Description |
|
All config server commands should be idempotent, to handle config server primary stepdown. Currently, enableSharding, a command in the process of being moved to config from mongos, returns an AlreadyInitialized error when there is an attempt to retry the command. This ticket should make the command return the same status as the first run. Additionally, update the enableSharding unit test expecting the AlreadyInitialized error to reflect this change. |
| Comments |
| Comment by Githook User [ 22/Jul/17 ] |
|
Author: {u'name': u'Jessica Yu', u'email': u'jessica.yu@mongodb.com'}Message: |