[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: |
|
||||||||||||||||
| 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 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 |
| 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. |