jstests/sharding/kill_sessions.js doesn't wait for operation to be killed.

XMLWordPrintableJSON

    • None
    • None
    • None
    • None
    • None
    • None

      The code that actually does the killing on mongod is here, which ultimately calls ServiceContext->killOperation and OperationContext->interrupt. It looks like this only marks the OpContext to be killed, but doesn't wait for the command to actually finish.

      The test is written in a way that assumes that the command is synchronous. Assert.soon in the test will be able to fix this if the command actually should be async.

              Assignee:
              Blake Oler
              Reporter:
              Lamont Nelson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: