[SERVER-34261] "Detach" stuck threads in ServiceExecutorAdaptive Created: 02/Apr/18 Updated: 06/Dec/22 Resolved: 02/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Sprint: | Platforms 2018-04-09, Platforms 2018-04-23 |
| Participants: |
| Description |
|
There are a few optimizations along this theme. The primary goal is to dismiss most of the overhead of managing stuck threads. They should be removed from the iterated list of ThreadStates at the least and probably should be set to stop work cycles after the current task is finished. This also means we should be checking "stuckness" either as a local thread state property set from indicator functions or by detecting overly long runtime for a given task. In either case, the changeover from normal thread to "detached" should be handled by the controller thread. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ] |
|
The Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable. |