# UpdateRequest upsert with retryOnConflict using BulkProcessor failed

**URL:** <https://discuss.elastic.co/t/updaterequest-upsert-with-retryonconflict-using-bulkprocessor-failed/182455>\
**Category:** Elasticsearch\
**Created:** [May 23, 2019, 1:45pm UTC](https://discuss.elastic.co/t/updaterequest-upsert-with-retryonconflict-using-bulkprocessor-failed/182455 "2019-05-23T13:45:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![yelin](https://avatars.discourse-cdn.com/v4/letter/y/e274bd/32.png) [@yelin](https://discuss.elastic.co/u/yelin)\
**Post date:** [May 24, 2019, 2:56pm UTC](https://discuss.elastic.co/t/updaterequest-upsert-with-retryonconflict-using-bulkprocessor-failed/182455/5 "2019-05-24T14:56:16Z")

</div>

I got similar issue before even though we're using both 6.x server & client, reported on the forum but didn't get any feedback. As I'm using org.elasticsearch.action.bulk.BulkProcessor, for which alternatively you can set the number of retries through BulkProcessor.Builder.setBackoffPolicy() (example at [https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-high-document-bulk.html#java-rest-high-document-bulk-processor](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-high-document-bulk.html#java-rest-high-document-bulk-processor)). However, for you to be aware of, there is another bug on the BulkProcessor reported at [BulkProcessor hangs instead of timeout](https://discuss.elastic.co/t/bulkprocessor-hangs-instead-of-timeout/147737), which doesn't seem resolved yet ☹

---

_[View the full topic](https://discuss.elastic.co/t/updaterequest-upsert-with-retryonconflict-using-bulkprocessor-failed/182455)._