revisit if thread marked as unkillable is okay to be killable for sharding related

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Cluster Scalability Priorities
    • 200
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-70127, we changed the default behavior of a thread to be killable by default by stepdown. 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.

      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-74658) to lookup TODO threads.

        1.
        		 (Catalog and Routing) Revisit if thread marked as unkillable is okay to be killable SERVER-111753 Sub-task Backlog Unassigned  
        2.
        		 (Replication) Revisit if thread marked as unkillable is okay to be killable SERVER-111754 Sub-task Needs Scheduling Unassigned  
        3.
        		 (Server Programmability) Revisit if thread marked as unkillable is okay to be killable SERVER-111755 Sub-task Needs Scheduling Unassigned  

            Assignee:
            Unassigned
            Reporter:
            Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: