[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: |
|
||||||||||||||||||||
| 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. |