From db1c41b41da54dc69d17af7290c2a3e544fabfe3 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Wed, 25 Dec 2024 08:17:18 -0700 Subject: [PATCH] (Doc+) Enrich run on ingest+data nodes not coordinating-only (#119136) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * (Doc+) Enrich run on ingest+data nodes not coordinating-only 👋 howdy, team! I'm not otherwise finding it so documenting https://github.com/elastic/elasticsearch/issues/95969 in ES docs > Currently we tell users of enrich that they should co-locate the nodes that perform the enrichment (ingest nodes) with the actual enrich data so that enrich operations don't require a remote search operation. * feedback Co-authored-by: Lee Hinman --------- Co-authored-by: Lee Hinman --- docs/reference/ingest/enrich.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/ingest/enrich.asciidoc b/docs/reference/ingest/enrich.asciidoc index 4bd50641149c0..3c08384eb23db 100644 --- a/docs/reference/ingest/enrich.asciidoc +++ b/docs/reference/ingest/enrich.asciidoc @@ -98,7 +98,8 @@ and <>. [IMPORTANT] ==== The enrich processor performs several operations and may impact the speed of -your ingest pipeline. +your ingest pipeline. We recommend <> co-locating +ingest and data roles to minimize remote search operations. We strongly recommend testing and benchmarking your enrich processors before deploying them in production.