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

killop not robust

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 1.7.2
    • None
    • Usability
    • None
    • 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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: