[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:
https://github.com/mongodb/mongo/blob/a2af071c5a28f2d92179ac20ac2d163043db19b9/src/mongo/db/s/resharding/resharding_recipient_service.cpp#L207
https://github.com/mongodb/mongo/blob/a2af071c5a28f2d92179ac20ac2d163043db19b9/src/mongo/db/s/resharding/resharding_coordinator_service.cpp#L1044
https://github.com/mongodb/mongo/blob/a2af071c5a28f2d92179ac20ac2d163043db19b9/src/mongo/db/s/resharding/resharding_donor_service.cpp#L229

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.

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