Fix killOperation race in AsyncOpTimeoutWithOpCtxDeadlineLater NITL test

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • Fully Compatible
    • ALL
    • N&O 2025-04-14, N&O 2025-04-28
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If the main thread executes the assertion on command counts after the NITL thread has successfully run killOperation for the request that timed out, then it will see one more successful command than expected and fail. This can be deterministically reproduced with a 100ms sleep here: https://github.com/mongodb/mongo/blob/0a68308f0d39a928ed551f285ba72ca560c38576/src/mongo/executor/network_interface_integration_test.cpp#L873 

      Make the test shutdown the NITL before asserting on command counts to ensure it is done with all work.

              Assignee:
              Joseph Prince
              Reporter:
              Erin McNulty
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: