Make the remote command execution in ReplicationExecutor::NetworkInterface asynchronous

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 2.7.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This facilitates testing, and nearly obviates the need for a thread pool in the ReplicationExecutor itself. The implementation in mongod of the NetworkInterface will continue to use a thread pool for now, but it's no longer required, and the one in the unit tests will be thread-pool free. This makes it easier to write deterministic unit tests of network activity.

            Assignee:
            Andy Schwerin
            Reporter:
            Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: