# Enrich Processor is slow on multi nodes

**URL:** <https://discuss.elastic.co/t/enrich-processor-is-slow-on-multi-nodes/260245>\
**Category:** Elasticsearch\
**Tags:** ingest-pipeline\
**Created:** [January 5, 2021, 5:03pm UTC](https://discuss.elastic.co/t/enrich-processor-is-slow-on-multi-nodes/260245 "2021-01-05T17:03:57Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Alain\_St\_Pierre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alain_st_pierre/32/81083_2.png) [@Alain\_St\_Pierre](https://discuss.elastic.co/u/Alain_St_Pierre)\
**Post date:** [January 6, 2021, 12:24am UTC](https://discuss.elastic.co/t/enrich-processor-is-slow-on-multi-nodes/260245/9 "2021-01-06T00:24:50Z")

</div>

Hey guys... I am working with Mike on this...

We have a Lambda function executing the enrich policy daily. This keeps the enrich index fresh as the source index is constantly being updated. When I remove the enrich processor, we are able to ingest successfully with multiple nodes (even across AZ's).

This issue is related to a thread I started here: [ES Cloud - Running ingest pipelines on warm nodes?](https://discuss.elastic.co/t/es-cloud-running-ingest-pipelines-on-warm-nodes/259054/4)

---

_[View the full topic](https://discuss.elastic.co/t/enrich-processor-is-slow-on-multi-nodes/260245)._