Refactor OplogFetcher to not use DBClientConnection

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: