# Multiple fast consecutive updates on the same document

**URL:** <https://discuss.elastic.co/t/multiple-fast-consecutive-updates-on-the-same-document/274595>\
**Category:** Elasticsearch\
**Created:** [June 1, 2021, 8:26am UTC](https://discuss.elastic.co/t/multiple-fast-consecutive-updates-on-the-same-document/274595 "2021-06-01T08:26:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Niels\_Theen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niels_theen/32/89557_2.png) [@Niels\_Theen](https://discuss.elastic.co/u/Niels_Theen)\
**Post date:** [June 1, 2021, 8:26am UTC](https://discuss.elastic.co/t/multiple-fast-consecutive-updates-on-the-same-document/274595/1 "2021-06-01T08:26:37Z")

</div>

Hi there,

I hope someone can help me with a very specific problem I have.

We integrated Elasticsearch in our multi-tenant-system.

Based on our system we forced to use `update_by_query` instead of `update`.

This system creates multiple consecutive updates to Elasticsearch for the same document in under 1 second.  
Because of this we will lose some data from requests because some updates are not executed.  
I guess that the data is lost becuase a document is available for new updates in 1 second.

Now my question: Is there any possibility that these request are not lost? Is there some kind of cache that can be activated that I overlooked in the documentation?

---

<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:** [June 29, 2021, 8:27am UTC](https://discuss.elastic.co/t/multiple-fast-consecutive-updates-on-the-same-document/274595/2 "2021-06-29T08:27:31Z")

</div>

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