[SERVER-74657] revisit if thread marked as unkillable is okay to be killable for storage execution related Created: 07/Mar/23  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jiawei Yang Assignee: Daotang Yang
Resolution: Unresolved Votes: 0
Labels: storex-ranked, storex-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-70127 Default system operations to be killa... Closed
Related
related to SERVER-79026 Failing to cancel the JournalFlusher ... Closed
is related to SERVER-73036 Investigate potential deadlock with i... Closed
Assigned Teams:
Storage Execution
Sprint: Execution Team 2024-02-05, Execution Team 2024-02-19
Participants:

 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.

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


Generated at Thu Feb 08 06:28:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.