# Does elasticsearch Ingest processor need to be thread safe?

**URL:** <https://discuss.elastic.co/t/does-elasticsearch-ingest-processor-need-to-be-thread-safe/68084>\
**Category:** Elasticsearch\
**Created:** [December 5, 2016, 6:25pm UTC](https://discuss.elastic.co/t/does-elasticsearch-ingest-processor-need-to-be-thread-safe/68084 "2016-12-05T18:25:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lin-zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lin-zhao/32/11147_2.png) [@lin-zhao](https://discuss.elastic.co/u/lin-zhao)\
**Post date:** [December 5, 2016, 6:25pm UTC](https://discuss.elastic.co/t/does-elasticsearch-ingest-processor-need-to-be-thread-safe/68084/1 "2016-12-05T18:25:13Z")

</div>

I'm developing a custom ingest processor. Does it need to be thread safe? Would there be concurrent [Processor.execute()](https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/ingest/Processor.java#L38) calls to the same processor instance?

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [December 6, 2016, 9:04am UTC](https://discuss.elastic.co/t/does-elasticsearch-ingest-processor-need-to-be-thread-safe/68084/2 "2016-12-06T09:04:56Z")

</div>

Hi @lin-zhao,

yes, ingest processors need to be thread safe. We'll enhance the Javadocs to make that clear. Thanks for the catch!

Daniel

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 3, 2017, 9:05am UTC](https://discuss.elastic.co/t/does-elasticsearch-ingest-processor-need-to-be-thread-safe/68084/3 "2017-01-03T09:05:02Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
