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

CurOp::_killPending not always cleared between client operations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Gone away
    • Affects Version/s: 2.5.1
    • Fix Version/s: None
    • Component/s: Internal Code
    • Labels:
      None
    • Operating System:
      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

          Issue Links

          is depended on by

          New Feature - A new feature of the product, which has yet to be developed. SERVER-2212 Server automatically abort queries/commands after user-specified time limit

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-14758 killOp on foreground index build does not take effect until the end of the index build

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: