# Elasticsearch filter plugin and pipeline workers race condition

**URL:** <https://discuss.elastic.co/t/elasticsearch-filter-plugin-and-pipeline-workers-race-condition/252862>\
**Category:** Logstash\
**Created:** [October 21, 2020, 3:22pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-and-pipeline-workers-race-condition/252862 "2020-10-21T15:22:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rfferrao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rfferrao/32/76344_2.png) [@rfferrao](https://discuss.elastic.co/u/rfferrao)\
**Post date:** [October 21, 2020, 3:22pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-and-pipeline-workers-race-condition/252862/1 "2020-10-21T15:22:38Z")

</div>

I'm considering migrating the `aggregate` filter towards a query through the `elasticsearch` filter plugin in favor of managing parent/child relationships between sets of data.

Since I'll be backtracking in search of the starting document that defines the event, I'm worried that there may be some race condition issues while using multiple `pipeline.workers`.

Is there any recommendations when it comes to this type of scenario? If this is too vague, I can provide some more details and examples of what we're dealing with here.

Thanks.

---

<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:** [November 18, 2020, 3:22pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-and-pipeline-workers-race-condition/252862/2 "2020-11-18T15:22:47Z")

</div>

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