[SERVER-84465] Use a ThreadPool so that we can track all thread ids and eventually collect their stack traces. Created: 29/Dec/23 Updated: 29/Dec/23 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sandeep Dhoot | Assignee: | Backlog - Atlas Streams |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Atlas Streams
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Instead of creating individual threads, we should use a ThreadPool to spawn any threads for stream execution. This will also allow us to track thread ids of these threads which we can use to get their stack traces. |