[SERVER-52722] Handle cloning restart in TenantMigrationRecipientService Created: 09/Nov/20 Updated: 29/Oct/23 Resolved: 04/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-E | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2021-01-25, Repl 2021-02-08 |
| Participants: |
| Description |
|
Handle the case where a 'startFetchingOpTime' exists in the state on restart of the service, but not a 'cloneFinishedOpTime', by choosing a new donor sync source, restarting the oplog buffer, restarting oplog fetching, and restarting cloning. |
| Comments |
| Comment by Githook User [ 04/Feb/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |