[SERVER-32089] Support rename collections during initial sync by retrying Created: 27/Nov/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 63 | ||||||||||||||||||||||||||||
| Description |
|
If a collection is renamed during initial sync, the getMore will return an error (either CursorNotFound or OperationFailed). We can detect that this is due to a rename doing a find by UUID; if the find is successful the response contains the new name. If we respond to this by re-starting the clone and persisting it locally to the old name, initial sync will work correctly with the rename being applied later during oplog application. |
| Comments |
| Comment by Judah Schvimer [ 06/Aug/19 ] |
|
We believe that this will be solved by (or require minimal work after) the Resumable Initial Sync project. Putting on the backlog for now. |