[SERVER-74656] revisit if thread marked as unkillable is okay to be killable for replication related Created: 06/Mar/23  Updated: 29/Oct/23  Resolved: 20/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: Sean Zimmerman
Resolution: Fixed Votes: 0
Labels: repl-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:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-04-03, Repl 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-74656) to lookup TODO threads.



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

Author:

{'name': 'seanzimm', 'email': 'sean.zimmerman@mongodb.com', 'username': 'seanzimm'}

Message: SERVER-74656: Address unkillable replication threads
Branch: master
https://github.com/mongodb/mongo/commit/640cd62374492b5a066c4d4fa78c76db97e21ad9

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