[SERVER-42950] Make _configsvrRefineCollectionShardKey return if shard key is already refined before checking for StaleEpoch Created: 21/Aug/19 Updated: 29/Oct/23 Resolved: 21/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.3 Required |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Heppenstall (Inactive) | Assignee: | James Heppenstall (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: | Sharding 2019-08-26 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
A config server stepdown may cause the mongos to retry _configsvrRefineCollectionShardKey even though it has successfully refined the shard key. This results in a StaleEpoch error. Checking that the shard key has already been refined before checking for a StaleEpoch error will fix this bug. |
| Comments |
| Comment by Githook User [ 21/Aug/19 ] |
|
Author: {'username': 'JamesHeppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'name': 'Jamie Heppenstall'}Message: |