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

CurOp::_killPending not always cleared between client operations

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • 2.5.1
    • Internal Code
    • None
    • ALL

    Description

      CurOp::_reset() is not called before running $cmd.sys operations. This can cause $cmd.sys operations to be erroneously killed if they are run directly following another operation that is killed. The interruption could occur, for example, in an auth-enabled system during the killCurrentOp.checkForInterrupt() call in BtreeCursor::advance(), if the authorization check for the $cmd.sys op has to fetch a privilege document from disk.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rassi J Rassi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: