CurOp::_killPending not always cleared between client operations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.5.1
    • Component/s: Internal Code
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Unassigned
              Reporter:
              J Rassi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: