[DOCS] Adds xpack.ml.max_ml_node_size #66285
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pinging @elastic/ml-core (:ml) |
|
Pinging @elastic/es-docs (Team:Docs) |
benwtrent
reviewed
Dec 14, 2020
Comment on lines
83
to
87
| `xpack.ml.max_ml_node_size`:: | ||
| (<<static-cluster-setting,Static>>) | ||
| The maximum node size for {ml} nodes. Defaults to `0b`, which means this value | ||
| is ignored. | ||
|
|
There was a problem hiding this comment.
This is an advanced setting that should only be set if the way that ES is deployed allows for automatic cluster scaling. This setting should be set to the maximum possible future node. This way when assigning a ML job to a node (and it is lazily assignable), we can fail quickly as we know that scaling will never support a job of this size.
There was a problem hiding this comment.
Thanks, I've taken another crack at adding those details and moved it down to the advanced settings.
droberts195
reviewed
Dec 14, 2020
| @@ -80,6 +80,11 @@ total memory of the machine, not current free memory. Jobs are not allocated to | |||
| a node if doing so would cause the estimated memory use of {ml} jobs to exceed | |||
| the limit. | |||
|
|
|||
| `xpack.ml.max_ml_node_size`:: | |||
| (<<static-cluster-setting,Static>>) | |||
There was a problem hiding this comment.
It’s dynamic now (changed earlier today)
benwtrent
approved these changes
Dec 16, 2020
lcawl
added a commit
to lcawl/elasticsearch
that referenced
this pull request
Dec 16, 2020
lcawl
added a commit
to lcawl/elasticsearch
that referenced
this pull request
Dec 16, 2020
This was referenced Dec 16, 2020
lcawl
added a commit
that referenced
this pull request
Dec 17, 2020
lcawl
added a commit
that referenced
this pull request
Dec 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #59309 and #66132
Adds xpack.ml.max_ml_node_size to the machine learning settings documentation