[SERVER-48582] Change StaleConfig error code in 'newlyAdded' field removal reconfig Created: 04/Jun/20 Updated: 29/Oct/23 Resolved: 04/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Vesselina Ratcheva (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 | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2020-06-15 | ||||||||
| Participants: | |||||||||
| Description |
|
While it sounds right for the situtation, it is very much a sharding-specific error. This is actually one of the codes that requires an ExtraErrorInfo object; the StaleConfig version of that (StaleConfigInfo) needs real sharding info, like the shardId, which we do not (and should not) have access to in the ReplicationCoordinator. The simplest solution is to just replace this error code with a different one. |
| Comments |
| Comment by Githook User [ 04/Jun/20 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |