[SERVER-61180] Refactor OplogFetcher to not use DBClientConnection Created: 02/Nov/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
It is hard to unit-test our code with mix of DBClientConnection and other network components. And DBClientConnection is not async-friendly. Now that we have more support (e.g. exhaust cursors) in executors, we should switch to that so our code looks more similar to other subsystems in the server. |