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.

Sign up for GitHub

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

Jump to bottom

[DOCS] Adds xpack.ml.max_ml_node_size #66285

Merged
merged 3 commits into from
Dec 16, 2020
Merged

[DOCS] Adds xpack.ml.max_ml_node_size #66285

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3abb084
[DOCS] Adds xpack.ml.max_ml_node_size
lcawl Dec 14, 2020
ac61994
[DOCS] Clarify setting description
lcawl Dec 14, 2020
a708d56
[DOCS] Changes static setting to dynamic
lcawl Dec 14, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/reference/settings/ml-settings.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,14 @@ IMPORTANT: This setting assumes some external process is capable of adding {ml}
nodes to the cluster. This setting is only useful when used in conjunction with
such an external process.

`xpack.ml.max_ml_node_size`::
(<<cluster-update-settings,Dynamic>>)
The maximum node size for {ml} nodes in a deployment that supports automatic
cluster scaling. Defaults to `0b`, which means this value is ignored. If you set
it to the maximum possible size of future {ml} nodes, when a {ml} job is
assigned to a lazy node it can check (and fail quickly) when scaling cannot
support the size of the job.

`xpack.ml.process_connect_timeout`::
(<<cluster-update-settings,Dynamic>>) The connection timeout for {ml} processes
that run separately from the {es} JVM. Defaults to `10s`. Some {ml} processing
Expand Down