audit interrupt points for new query system runners

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.5.4
    • Component/s: Querying
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Right now the query system doesn't do a good job of checking whether the operation has been killed using

      killCurrentOp.checkForInterrupt()
      

      This can make it impossible to kill long-running queries. Runners should check for interrupt inside their getNext() method.

            Assignee:
            David Storch
            Reporter:
            David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: