[SERVER-52723] Handle oplog application restart in TenantMigrationRecipientService Created: 09/Nov/20  Updated: 29/Oct/23  Resolved: 26/Jan/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

Issue Links:
Problem/Incident
Related
is related to SERVER-60872 Deadlock between stepDown and TenantO... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-12-28, Repl 2021-01-11, Repl 2021-01-25, Repl 2021-02-08
Participants:
Linked BF Score: 24

 Description   

Handle the case where a 'startFetchingOpTime' and a 'cloneFinishedOpTime' exist in the TenantMigrationRecipientService state upon restart, by choosing a new donor sync source, restarting the oplog buffer, restarting oplog fetching, and restarting oplog application. This includes searching back through the oplog to find the point at which oplog application should start.



 Comments   
Comment by Githook User [ 26/Jan/21 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}

Message: SERVER-52723 Handle oplog application restart in TenantMigrationRecipientService
Branch: master
https://github.com/mongodb/mongo/commit/3b87ecca61a77614d03f01a36a6ea4e155917ff0

Generated at Thu Feb 08 05:28:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.