# Ideas to avoid double indexing when using rollover indice

**URL:** <https://discuss.elastic.co/t/ideas-to-avoid-double-indexing-when-using-rollover-indice/176663>\
**Category:** Elasticsearch\
**Created:** [April 12, 2019, 3:38pm UTC](https://discuss.elastic.co/t/ideas-to-avoid-double-indexing-when-using-rollover-indice/176663 "2019-04-12T15:38:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bao\_Tran1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bao_tran1/32/44040_2.png) [@Bao\_Tran1](https://discuss.elastic.co/u/Bao_Tran1)\
**Post date:** [April 12, 2019, 3:38pm UTC](https://discuss.elastic.co/t/ideas-to-avoid-double-indexing-when-using-rollover-indice/176663/1 "2019-04-12T15:38:37Z")

</div>

Hi there,

I am testing the rollover feature to address our big indice issue. I can see the issue of double indexing.

Basically, our app sends bulk request to cluster. The app would retry the bulk request if any errors (failed or partially failed). We use guid as doc id to make sure our write is upsert.

As in this scenario, the retry will happen in either network latency when receiving ack or partial failed bulk. If we use rollover, there is a highly chance the original write went to old indice and the retry would go to new rolled indice. We can't afford duplicate documents on searching. What are the solutions for this issue?

Thank you!

---

<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 10, 2019, 3:38pm UTC](https://discuss.elastic.co/t/ideas-to-avoid-double-indexing-when-using-rollover-indice/176663/2 "2019-05-10T15:38:46Z")

</div>

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