Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] Put the auto calculation of capacity behind a feature flag, for now (#195390) #195486

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…lastic#195390)

In this PR, I'm preparing for the 8.16 release where we'd like to start
rolling out the `mget` task claiming strategy separately from the added
concurrency. To accomplish this, we need to put the capacity calculation
behind a feature flag that is default to false for now, until we do a
second rollout with an increased concurrency. The increased concurrency
can be calculated and adjusted based on experiments of clusters setting
`xpack.task_manager.capacity` to a higher value and observe the resource
usage.

PR to deploy to Cloud and verify that we always default to 10 normal
tasks: elastic#195392

(cherry picked from commit 9c8f689)
@kibanamachine kibanamachine merged commit 59444d0 into elastic:8.x Oct 8, 2024
32 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @mikecote

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants