# Updating documents with deterministic ID in older index after rollover

**URL:** <https://discuss.elastic.co/t/updating-documents-with-deterministic-id-in-older-index-after-rollover/230313>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [April 29, 2020, 6:34am UTC](https://discuss.elastic.co/t/updating-documents-with-deterministic-id-in-older-index-after-rollover/230313 "2020-04-29T06:34:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomasz\_Szymanski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomasz_szymanski/32/45910_2.png) [@Tomasz\_Szymanski](https://discuss.elastic.co/u/Tomasz_Szymanski)\
**Post date:** [April 29, 2020, 6:34am UTC](https://discuss.elastic.co/t/updating-documents-with-deterministic-id-in-older-index-after-rollover/230313/1 "2020-04-29T06:34:50Z")

</div>

Hi Guys,

I have system where I retrieve data from different sources from .NET project, put it on a rabbitmq queue, grab them from logstash, and logstash indexes these data in my elasticsearch.

Recently I introduced index-lifecycle-managment to rollover the indexes when they grow too big. Which worked fine until l encountered following issue.

My data have deterministic GUID IDs, when my index rollover there is a probability that the data that are supposed to be indexed are already in ROLLED index. This is a must, because I am updating some of these data, and their GUID IDs are generated deterministically.

So basically, I do not want data that IDs are already in old indexes to be indexed in new index, I want them updated in old appropriate index.

Do you have any suggestions on how to overcome this issue?  
I can provide logstash and elasticsearch ILM policy/template configs if needed.

---

<div class="post-metadata">

**Author:** ![DaroH](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@DaroH](https://discuss.elastic.co/u/DaroH)\
**Post date:** [April 30, 2020, 7:34am UTC](https://discuss.elastic.co/t/updating-documents-with-deterministic-id-in-older-index-after-rollover/230313/2 "2020-04-30T07:34:26Z")

</div>

This is an issue we encountered recently as well, but havent found satisfying solution yet. Anyone have any input on this?

---

<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:** [April 30, 2020, 8:28am UTC](https://discuss.elastic.co/t/updating-documents-with-deterministic-id-in-older-index-after-rollover/230313/3 "2020-04-30T08:28:42Z")

</div>

Assuming you have a time stamp associated with each document which you can use to determine index, I would recommend using ILM without rollover.

---

<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:** [May 28, 2020, 8:28am UTC](https://discuss.elastic.co/t/updating-documents-with-deterministic-id-in-older-index-after-rollover/230313/4 "2020-05-28T08:28:50Z")

</div>

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