[SERVER-74662] Query work to revisit if threads currently marked as "unkillable"(meaning non-interruptible) should instead be interruptable Created: 07/Mar/23 Updated: 29/Oct/23 Resolved: 21/Aug/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: | Rushan Chen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QE 2023-05-15, QE 2023-05-29, QE 2023-06-12, QE 2023-06-26, QE 2023-07-10, QE 2023-07-24, QE 2023-08-07, QE 2023-08-21, QE 2023-09-04 | ||||||||
| Participants: | |||||||||
| Description |
|
InĀ Here killable means interruptable. The thread itself is not canceled if the interrupt is handled. 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( |
| Comments |
| Comment by Githook User [ 18/Aug/23 ] |
|
Author: {'name': 'Rushan Chen', 'email': 'rushan.chen@mongodb.com', 'username': 'ruchen'}Message: |
| Comment by Rushan Chen [ 25/May/23 ] |
|
I marked the spreadsheet based on the what little I can find in the header files. There is no one on my team who has deeper knowledge than trying to gleam clues from the code. Probably best to have another person taking a look. Separately, is marking the spreadsheet the action to be performed by this audit? It's not clear what "Non Action" and "server ticket" means in the column heading so I just marked whether threads should be non killable or not. |
| Comment by Ana Meza [ 14/Mar/23 ] |
|
Passing this to query-director-triage to assign priority |
| Comment by Kyle Suarez [ 07/Mar/23 ] |
|
jiawei.yang@mongodb.com, as your other ticket is still in code review, I am leaving this in the triage queue. (At first glance, though, it seems like the ClientCursorMonitor and some strange thread in DocumentSourceOut are the query-related ones so far. The ClientCursorMonitor should not be killed, though.) |