[SERVER-32336] Update applyOps to use new Applier interface for oplog application Created: 14/Dec/17 Updated: 06/Dec/22 Resolved: 17/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory McKeon (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Comments |
| Comment by A. Jesse Jiryu Davis [ 17/Oct/19 ] |
|
Currently applyOps hooks into the rest of the replication system by calling applyOperation_inlock. I think that's correct, applyOps has so much quirky behavior that trying to factor it with OplogApplier would be risky and probably make the code less maintainable. |
| Comment by Judah Schvimer [ 17/Oct/19 ] |
|
jesse, does this provide much value anymore, or can we close this? |