[SERVER-68279] Set min thread pool size for CancelableOperationContext in resharding to 0 Created: 25/Jul/22 Updated: 18/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam1, neweng, sharding-nyc-subteam1, tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Participants: | |
| Story Points: | 2 |
| Description |
|
The current setting is 1: This means that there's at least 1 thread in standby dedicated just for calling markKilled on the opCtx when the cancellation token is cancelled. |
| Comments |
| Comment by Max Hirschhorn [ 15/Aug/22 ] |
|
We should probably also take a moment to extract this pattern of constructing the thread pool for the _markKilledExecutor in each of the resharding primary-only services to a helper function. |