[SERVER-43887] Investigate removal of MultiApplier Created: 08/Oct/19 Updated: 06/Dec/22 Resolved: 06/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mihai Andrei | 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 | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Currently, MultiApplier is only used in Initial Sync as a thin wrapper around OplogApplier. Look into whether it is safe to remove MultiApplier entirely and simply use the OplogApplier in Initial Sync. |
| Comments |
| Comment by Judah Schvimer [ 06/Dec/19 ] |
|
We'll reopen if this becomes a pain point. |
| Comment by A. Jesse Jiryu Davis [ 14/Oct/19 ] |
|
It's possible that MultiApplier was more widely used pre-4.2, investigate the history. |