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

killop not robust

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.2
    • Component/s: Usability
    • Labels:
      None
    • Operating System:
      ALL

      Description

      The current killop implementation only tracks the op num of the most recently requested op to kill. This means that if I kill op 5 and then kill op 6 immediately afterward, and the execution of op 5 happens not to call checkForInterrupt() between the two killop requests, op 5 will not be killed.

      It also appears there may be an issue if the op num of the last killed op is reused. It's possible that the op with the reused num will be killed immediately upon starting, though I haven't confirmed this with a test.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              eliot Eliot Horowitz (Inactive)
              Reporter:
              aaron Aaron Staple
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: