[SERVER-22935] Add JS/client function to retry moveChunk on mongod stepdown related errors Created: 02/Mar/16 Updated: 06/Dec/22 Resolved: 20/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
If a moveChunk operation fails because one of the mongods involved in the migration (donor or recipient) stepped down, the client should retry the moveChunk operation. *NOTE* |
| Comments |
| Comment by Kaloian Manassiev [ 20/Jul/16 ] |
|
This retry functionality will not be necessary once all migrations (both manual and automatic) go through the CSRS primary. |