Skip to content

[7.x] [ML] make xpack.ml.max_ml_node_size and xpack.ml.use_auto_machine_memory_percent dynamically settable (#66132) #66270

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

Merged
merged 1 commit into from
Dec 14, 2020

Conversation

benwtrent
Copy link
Member

Backports the following commits to 7.x:

…memory_percent` dynamically settable (elastic#66132)

With this commit the following settings are all dynamic:

- `xpack.ml.max_ml_node_size`
- `xpack.ml.use_auto_machine_memory_percent`
- `xpack.ml.max_lazy_ml_nodes`

Since all these settings could be easily interrelated, the ability to update a Cluster with a single settings call is useful.

Additionally, setting some of these values at the node level (in a new node in a mixed cluster) it could cause issues with the master attempting to read the newer setting/value.
@benwtrent benwtrent added :ml Machine learning backport labels Dec 14, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@benwtrent benwtrent merged commit f2f04b2 into elastic:7.x Dec 14, 2020
@benwtrent benwtrent deleted the backport/7.x/pr-66132 branch December 14, 2020 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :ml Machine learning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants