# Delete by query , refresh=wait\_for support?

**URL:** <https://discuss.elastic.co/t/delete-by-query-refresh-wait-for-support/154118>\
**Category:** Elasticsearch\
**Created:** [October 26, 2018, 7:05am UTC](https://discuss.elastic.co/t/delete-by-query-refresh-wait-for-support/154118 "2018-10-26T07:05:36Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\
**Post date:** [October 26, 2018, 12:10pm UTC](https://discuss.elastic.co/t/delete-by-query-refresh-wait-for-support/154118/6 "2018-10-26T12:10:21Z")

</div>

> [@Grievoushead](#):
>
> Anyhow, I have another questions: `?retry_on_conflict=3` param which doesn't work for delete\_by\_query but works for update.

IMO retry\_on\_conflict is only used when updating a document, in this case, a conflict of version may occure. When you delete a doc, there is no conflic _"possible"_, the doc is deleted.

In the response, "retries" is when the initial request failed (cluster error, timeout, etc..), this is not a _version conflict_.

bye,  
Xavier

---

_[View the full topic](https://discuss.elastic.co/t/delete-by-query-refresh-wait-for-support/154118)._