Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-43210

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

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Activity

          People

            blake.oler@mongodb.com Blake Oler
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: