[SERVER-74660] revisit if thread marked as unkillable is okay to be killable for security related Created: 07/Mar/23  Updated: 29/Oct/23  Resolved: 21/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Jiawei Yang Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: None
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
is related to SERVER-78573 Make JWKSetRefresher killable Closed
Assigned Teams:
Server Security
Backwards Compatibility: Fully Compatible
Sprint: Security 2023-07-10, Security 2023-07-24
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-74660) to lookup TODO threads.



 Comments   
Comment by Githook User [ 18/Jul/23 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-74660 Make security threads handle interrupts gracefully
Branch: master
https://github.com/mongodb/mongo/commit/92945e81a7d3697ad9df26b4a8e831065f859f9a

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