Add CancellationToken support to NetworkInterfaceTL::startCommand

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • Fully Compatible
    • Networking & Obs 2024-08-19, Networking & Obs 2024-09-02, Networking & Obs 2024-09-16, Networking & Obs 2024-09-30, Networking & Obs 2024-10-14
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      With support for CancellationTokens in ConnectionPool (SERVER-92568) and in AsyncDBClient (SERVER-92569), we can now have NetworkInterfaceTL::startCommand pass a CancellationToken down to its asynchronous uses of ConnectionPool and AsyncDBClient. We should also consider whether there are any other places where cancellation should occur in both the exhaust and non-exhaust paths.

            Assignee:
            Joseph Prince
            Reporter:
            James Bronsted
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: