From 51b0b28d9edb0dce8e285796e73b43462f0db6c5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Wed, 29 Jan 2025 12:36:08 +0100 Subject: [PATCH] Update anomaly-detection-scale.asciidoc (#2922) As title states. (cherry picked from commit 727823d300b2ebd82bd7552f5602c591f17a086a) --- .../stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc b/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc index 5326b8567..d338f9101 100644 --- a/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc +++ b/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc @@ -65,7 +65,7 @@ size of a {ml} node. Creating {ml-jobs} with model memory limits larger than the maximum node size can support is not allowed, as autoscaling cannot add a node big enough to run the job. On a self-managed deployment, you can set `xpack.ml.max_model_memory_limit` according to the available resources of the -{ml} node. This prevents you from you creating jobs with model memory limits too +{ml} node. This prevents you from creating jobs with model memory limits too high to open in your cluster. [discrete]