[SERVER-33116] Split logOp functions out of oplog.cpp, move them into ReplicationOpObserver Created: 03/Feb/18  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: Spencer Brody (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32897 Separate ReplicationOpObserver from O... Backlog
depends on SERVER-33733 Remove all callers of repl::logOp fro... Backlog
Related
is related to SERVER-35906 Decouple the interfaces of the OpObse... Backlog
Assigned Teams:
Replication
Participants:

 Description   

No one should call logOp directly, all oplog entry writes should go through the OpObservers



 Comments   
Comment by Spencer Brody (Inactive) [ 28/Jun/18 ]

This, along with the linked tickets, are part of theme of work around refactoring the OpObserver subsystem. We made some changes to the OpObservers in 4.0 that left them in a bit of a weird state that is difficult to understand. Also transactions and other projects rely heavily on the OpObservers - making them easier to understand, use, and unit test would be a high value improvement to the code base.

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