# Elasticsearch delete\_by\_query version conflict

**URL:** <https://discuss.elastic.co/t/elasticsearch-delete-by-query-version-conflict/142492>\
**Category:** Elasticsearch\
**Created:** [August 1, 2018, 7:43am UTC](https://discuss.elastic.co/t/elasticsearch-delete-by-query-version-conflict/142492 "2018-08-01T07:43:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashishtiwari1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashishtiwari1993/32/135241_2.png) [@ashishtiwari1993](https://discuss.elastic.co/u/ashishtiwari1993)\
**Post date:** [August 1, 2018, 7:43am UTC](https://discuss.elastic.co/t/elasticsearch-delete-by-query-version-conflict/142492/1 "2018-08-01T07:43:46Z")

</div>

Hi guys,

My configuration is :  
Heap : 30GB  
core : 24  
ES version : 6

We having approx 100cr data (3 months) in single index. We have field date which has format 'yyyymmdd' . Data is pushing in realtime manner it this index. I want to keep deleting 3 months previous data ( where date \< 20180501). I am using 'delete\_by\_query' api. Because writing is going on while taking snapshot when hits 'delete\_by\_query' api, I am getting version conflict error. How i can tackle such situation without affecting my writing process. Thanks

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [August 2, 2018, 9:49am UTC](https://discuss.elastic.co/t/elasticsearch-delete-by-query-version-conflict/142492/2 "2018-08-02T09:49:19Z")

</div>

Have you thought about using more dated based indices? The reason I ask is that delete by query is much more expensive compared to just deleting an index from four months.

Also please see the docs [https://www.elastic.co/guide/en/elasticsearch/reference/6.3/docs-delete-by-query.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/docs-delete-by-query.html) and specifically the `conflicts` parameter

---

<div class="post-metadata">

**Author:** ![ashishtiwari1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashishtiwari1993/32/135241_2.png) [@ashishtiwari1993](https://discuss.elastic.co/u/ashishtiwari1993)\
**Post date:** [August 10, 2018, 10:07am UTC](https://discuss.elastic.co/t/elasticsearch-delete-by-query-version-conflict/142492/3 "2018-08-10T10:07:58Z")

</div>

@spinscale thanks for reply. I agree with you. If i am making index like index-jan, index-feb, index-mar and whenever i want to delete i can simply delete specific index of month, But what about my search query. Will be my search query will affected when i want to extract data from jan 01 to feb 10? It will query on both index OR it will affect my scroll queries ?

---

<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:** [September 7, 2018, 10:08am UTC](https://discuss.elastic.co/t/elasticsearch-delete-by-query-version-conflict/142492/4 "2018-09-07T10:08:00Z")

</div>

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