From 1092cfa26c04ffb61732371f3819d5f26968bf74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Fri, 5 Jul 2024 18:20:18 +0200 Subject: [PATCH] Adds important callout about the possibility of multiple ELSER deployment. (#2744) (cherry picked from commit b065d6118a23aeb1cf894f0ad5ac0d02491628a0) --- docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc b/docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc index 3596e58e4..6dee65f37 100644 --- a/docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc +++ b/docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc @@ -108,6 +108,14 @@ that walks through upgrading an index to ELSER V2. You can download and deploy ELSER either from **{ml-app}** > **Trained Models**, from **Search** > **Indices**, or by using the Dev Console. +IMPORTANT: You can deploy the model multiple times by assigning a unique +deployment ID when starting the deployment. It enables you to have dedicated +deployments for different purposes, such as search and ingest. By doing so, you +ensure that the search speed remains unaffected by ingest workloads, and vice +versa. Having separate deployments for search and ingest mitigates performance +issues resulting from interactions between the two, which can be hard to +diagnose. + [discrete] [[trained-model]]