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

Evaluate replacing NO_YIELD with INTERRUPT_ONLY

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2023-06-26, QE 2023-07-10, QE 2023-07-24, QE 2023-08-07, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13

    Description

      The existence of INTERRUPT_ONLY implies that there is a use case for a query not being interruptible, but all of our database operations should be interruptible. The task here is to try to remove NO_YIELD entirely and replace it with INTERRUPT_ONLY or at least understand why we still need NO_YIELD.

      Attachments

        Activity

          People

            rushan.chen@mongodb.com Rushan Chen
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: