Change thread pool to a ScalingExecutorBuilder #421
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changes Flow Framework thread pool to use a ScalingExecutorBuilder
FixedExecutorBuilder
establishes a maximum queue size which is arbitrary and not scalableResizableExecutorBuilder
allowing users to manually change this isn't used muchScalingExecutorBuilder
is widely used across OpenSearch and plugins and is clearly the preferred option here unless we know better. (Which we don't.)Matches "generic" thread pool type, with different number of processors since it's more narrowly focused.
Uses similar threadpool to AD except with shorter keepalive to correspond to most OpenSearch thread pool times, and uses full number of allocated processors (smaller # than generic).
Allows user to change # of processors per node via settings.
Issues Resolved
Fixes #420
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.