[SERVER-68192] Skip opening the backup cursor on migration retry if the migration already finished the (physical) cloning step Created: 20/Jul/22 Updated: 03/Mar/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | shard-merge-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
Skip the stages 1 and 2 on migration retry on the recipient side (caused due to recipient failover/donor failover) if the migration has already completed the (physical) cloning step |
| Comments |
| Comment by Suganthi Mani [ 03/Mar/23 ] |
|
Shard Merge not robust to donor/recipient failovers, restarts and rollbacks (see design doc). So, this ticket work is no longer needed |