[SERVER-32728] SyncTail::syncApply should accept OplogEntry instead of BSONObj for oplog Created: 16/Jan/18  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-32918 Make OplogEntry class useful for part... Closed
is related to SERVER-29200 Limit access to OplogEntry::raw Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Participants:

 Description   

After SERVER-29200, OplogEntry::raw is still referenced in the oplog application critical SyncTail::syncApply(). We should consider replacing the BSONObj argument with OplogEntry.



 Comments   
Comment by Siyuan Zhou [ 10/Aug/18 ]

After Benety's applier refactoring, the only place we access raw is when we write down the oplog entry on secondary, where it makes more sense to access raw than serializing it back for performance reasons.

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