[SERVER-53946] Resume batching from the last noop entry even if it is less than the startApplyingDonorOpTime Created: 21/Jan/21  Updated: 29/Oct/23  Resolved: 09/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: Jason Chan
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-H
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-53509 Create an oplog chain and update conf... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2021-03-08, Repl 2021-03-22
Participants:

 Description   

Currently, the tenant oplog batcher restarts from scratch if the last noop entry we find in the oplog is less than startApplyingDonorOpTime. SERVER-53509 will build the oplog chain for retryable writes when writing out noop entries and we do this even for oplog entries that are less than the startApplyingDonorOpTime. If we resume from the beginning, we may process those retryable writes multiple times.



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

Author:

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

Message: SERVER-53946 Resume batching from the last noop entry even if it is less than the startApplyingDonorOpTime
Branch: master
https://github.com/mongodb/mongo/commit/0c35e28c0d58d9119a1529218631410edd97aa7d

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