[SERVER-53198] Tenant oplog applier doesn't commit the no-op writes which can make tenant migration to hang. Created: 02/Dec/20  Updated: 29/Oct/23  Resolved: 03/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-B
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-12-14
Participants:
Linked BF Score: 22

 Description   

Currently, tenant oplog applier doesn't commit the no-op writes, but still forwarding the _lastAppliedOpTimesUpToLastBatch's recipient opTime. This can make the donor opTime waiters (recipientSyncData cmd) to hang indefinitely waiting on a recipient opTime that doesn't correspond to any oplog entry to be majority replicated.
+ Change streams are also affected as it won't be able to see the progress.



 Comments   
Comment by Githook User [ 03/Dec/20 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-53198 Tenant oplog applier should commit the no-op writes.
Branch: master
https://github.com/mongodb/mongo/commit/231ec13bcd4ba9962ec32999262f849decd8b556

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