[SERVER-45262] make IndexBuildsCoordinator thread pool configurable via startup parameter Created: 19/Dec/19  Updated: 27/Oct/23  Resolved: 20/Jul/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-44250 startIndexBuild oplog write and threa... Closed
is related to SERVER-44609 Replicate startIndexBuild oplog entry... Closed
is related to SERVER-44984 Reduce index thread pool size and red... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

The thread pool used by the IndexBuildsCoordinator to build indexes in the background is a resource that affect the availability of the server. Currently, this resource has a fixed size of 10, with tentative plans to reduce the default in SERVER-44984.

It would be useful for support and testing if we had a startup parameter to configure this resource.



 Comments   
Comment by Gregory Wlodarek [ 20/May/20 ]

benety.goh I think we can close this as SERVER-47155 made this configurable.

Comment by Sara Williamson [ 19/Dec/19 ]

In order to do this work we would need to make sure the thread pool always has one extra resource to unstick possible deadlocks.

Generated at Thu Feb 08 05:08:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.