-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-04-29, Execution Team 2024-05-13, Execution Team 2024-05-27, Execution Team 2024-06-10
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.
- depends on
-
SERVER-70127 Default system operations to be killable by stepdown
- Closed
- is related to
-
SERVER-73036 Investigate potential deadlock with index builds
- Closed
-
SERVER-91293 Make some unkillable threads killable
- Closed
- related to
-
SERVER-79026 Failing to cancel the JournalFlusher thread might lead to 3-way deadlock
- Closed