# Question about parallel updates

**URL:** <https://discuss.elastic.co/t/question-about-parallel-updates/371244>\
**Category:** Elasticsearch\
**Created:** [November 29, 2024, 6:39pm UTC](https://discuss.elastic.co/t/question-about-parallel-updates/371244 "2024-11-29T18:39:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yeikel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yeikel/32/125434_2.png) [@yeikel](https://discuss.elastic.co/u/yeikel)\
**Post date:** [November 29, 2024, 6:39pm UTC](https://discuss.elastic.co/t/question-about-parallel-updates/371244/1 "2024-11-29T18:39:50Z")

</div>

Hi team,

What is the expected behaviour if one client sends a batch request with the same document ID but different content?

Does Elasticsearch execute them in the order it received it, or does it do any deduplication?

Thank you

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 29, 2024, 7:38pm UTC](https://discuss.elastic.co/t/question-about-parallel-updates/371244/2 "2024-11-29T19:38:46Z")

</div>

Yes, they will be executed in order without any deduplication. Be aware that frequent updates to the same document has, at least in the past (not sure whether this is still an issue), potential to led to performance problems and increased overhead. It is therefore generally better to deduplicate before the batch is sent.
