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

Query work to revisit if threads currently marked as "unkillable"(meaning non-interruptible) should instead be interruptable

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2023-05-15, QE 2023-05-29, QE 2023-06-12, QE 2023-06-26, QE 2023-07-10, QE 2023-07-24, QE 2023-08-07, QE 2023-08-21, QE 2023-09-04

    Description

      InĀ SERVER-70127, we changed the default behavior of a thread to be killable by default. We now marked all threads that were not marked as killable before to be unkillable, but it could be there are threads not necessary to be unkillable.

      Here killable means interruptable. The thread itself is not canceled if the interrupt is handled.

      This ticket is created for teams owning relative code directories to revisit whether these threads should be marked as unkillable.

      You can search the ticket number(SERVER-74662) to lookup TODO threads.

      Attachments

        Activity

          People

            rushan.chen@mongodb.com Rushan Chen
            jiawei.yang@mongodb.com Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: