[SERVER-53508] Handle failover while fetching retryable writes before startFetchingOpTime Created: 23/Dec/20  Updated: 29/Oct/23  Resolved: 10/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-H
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-53319 Fetching retryable writes from before... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2021-03-08, Repl 2021-03-22
Participants:

 Description   

If the recipient fails over before it finishes writing all the oplog entries, the recipient can just throw out its oplog buffer and run the aggregate query again. This is acceptable because the amount of work the recipient will throw out is small compared to the total work for the migration, and failover is relatively rare.



 Comments   
Comment by Githook User [ 10/Mar/21 ]

Author:

{'name': 'Pavi Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com', 'username': 'pvselvan'}

Message: SERVER-53508 Handle recipient failover while fetching retryable writes from donor
Branch: master
https://github.com/mongodb/mongo/commit/a8a3bf12a9c056d26580623ff7a9c3401ac03fcf

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