[SERVER-47003] MaxTimeMSExceeded on _configsvrMoveChunk can lead to blocking future migrations for that chunk Created: 19/Mar/20 Updated: 29/Oct/23 Resolved: 30/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-common-backlog, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding EMEA 2022-12-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If moveChunk is sent with maxTimeMS, the following scenario can occur: If the config server gets another moveChunk attempt for that range, it will fail with DuplicateKeyError on config.migrations. config.migrations is keyed on namespace and the min value of the range being moved, so this will happen indefinitely for any chunk with the same min value. |
| Comments |
| Comment by Silvia Surroca [ 30/Dec/22 ] |
|
This bug was fixed by The existence of duplicated entry in config.migrations is managed here |