[SERVER-74661] revisit if thread marked as unkillable is okay to be killable for serverless related Created: 07/Mar/23  Updated: 29/Oct/23  Resolved: 14/Sep/23

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

Type: Improvement Priority: Major - P3
Reporter: Jiawei Yang Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: serverless-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
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-09-04, Server Serverless 2023-09-18
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-74661) to lookup TODO threads.



 Comments   
Comment by Githook User [ 14/Sep/23 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-74661 Audit unkillable threads by stepdown in Serverless code path.
Branch: master
https://github.com/mongodb/mongo/commit/c0af87c74fd301376b9e9bbb2ed85b804a900994

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