[SERVER-58374] Stop forcing routing info refresh in cluster moveChunk command Created: 08/Jul/21 Updated: 06/Dec/22 Resolved: 12/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Stop forcing a routing info refresh at the very beginning of cluster moveChunk command we should rely on the shard versioning protocol that will ensure that eventually the mongos will retry the command according to the updated routing info |