[SERVER-43731] Unify oplog visibility timestamp updates Created: 30/Sep/19  Updated: 06/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

Now, both initial syncer and oplog applier rely on calling oplogDiskLocRegister to update oplog visibility ts after calling multiApply. After SERVER-42925, idempotency tests also rely on oplogDiskLocRegister to mimic the server behavior. This makes it very easy for one to forget calling oplogDiskLocRegister. It seems that it is always the case that we want to update oplog visibility after oplog application. So it is probably a good idea to unify/merge the oplog visibility logic into multiApply.



 Comments   
Comment by A. Jesse Jiryu Davis [ 02/Oct/19 ]

I agree it's related, we can put it in the epic and make it an additional step towards the end of the steps in the "Address tech debt in Oplog Application Path" design doc.

Comment by Judah Schvimer [ 02/Oct/19 ]

jesse, would this make sense as part of, or strictly after the Oplog Application Tech Debt project? I don't want to increase the scope of that project too much, but this at least seems related.

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