# Delete by query, what's the behavior of conflicts=proceed

**URL:** https://discuss.elastic.co/t/delete-by-query-whats-the-behavior-of-conflicts-proceed/137062
**Category:** Elasticsearch
**Created:** [June 22, 2018, 5:39pm UTC](https://discuss.elastic.co/t/delete-by-query-whats-the-behavior-of-conflicts-proceed/137062 "2018-06-22T17:39:33Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Jinggang\_Diao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jinggang_diao/32/31917_2.png) [@Jinggang\_Diao](https://discuss.elastic.co/u/Jinggang_Diao)
#### Post date: [June 22, 2018, 5:39pm UTC](https://discuss.elastic.co/t/delete-by-query-whats-the-behavior-of-conflicts-proceed/137062/1 "2018-06-22T17:39:33Z")

</div>

If I have two servers sending the same delete by query request to a single ES server all the time. Two deletion tasks will always conflict with each other. If I have `conflicts=proceed`, what will really happen? My guess is, both tasks will be completed with response  
`{total: 1000000, deleted: someNum, version_conflicts = 1000000 - someNum}`  
and the other with response  
`{total:1000000, deleted:1000000 - someNum, version_conflicts = someNum}`.  
Am I right? How does `conflicts=proceed` really work?

---

<div class="post-metadata">

### Author: ![Jinggang\_Diao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jinggang_diao/32/31917_2.png) [@Jinggang\_Diao](https://discuss.elastic.co/u/Jinggang_Diao)
#### Post date: [June 30, 2018, 1:59am UTC](https://discuss.elastic.co/t/delete-by-query-whats-the-behavior-of-conflicts-proceed/137062/2 "2018-06-30T01:59:26Z")

</div>

Don't close the topic!

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 30, 2018, 6:37am UTC](https://discuss.elastic.co/t/delete-by-query-whats-the-behavior-of-conflicts-proceed/137062/3 "2018-06-30T06:37:55Z")

</div>

I think you're right.

This option just tells elasticsearch that in case of conflict (ie a document is updated or deleted in the meantime) it will continue to process the other documents.

---

<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: [July 28, 2018, 6:38am UTC](https://discuss.elastic.co/t/delete-by-query-whats-the-behavior-of-conflicts-proceed/137062/4 "2018-07-28T06:38:06Z")

</div>

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