# BulkProcessor does not retry on failures

**URL:** <https://discuss.elastic.co/t/bulkprocessor-does-not-retry-on-failures/163945>\
**Category:** Elasticsearch\
**Created:** [January 11, 2019, 6:11pm UTC](https://discuss.elastic.co/t/bulkprocessor-does-not-retry-on-failures/163945 "2019-01-11T18:11:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Clozel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brian_clozel/32/2448_2.png) [@Brian\_Clozel](https://discuss.elastic.co/u/Brian_Clozel)\
**Post date:** [January 11, 2019, 6:11pm UTC](https://discuss.elastic.co/t/bulkprocessor-does-not-retry-on-failures/163945/1 "2019-01-11T18:11:29Z")

</div>

As of [https://github.com/elastic/elasticsearch/issues/14620](https://github.com/elastic/elasticsearch/issues/14620), the `BulkProcessor` retries individual request failures. In case the Elasticsearch instance fails to respond or in case of a network error, the `RetryHandler` listener is called for the `onFailure` case.

This case does not trigger a retry and just fails right away.

In general, is this the expected behavior for bulk requests or should this be considered as an enhancement proposal?

---

<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:** [February 8, 2019, 6:11pm UTC](https://discuss.elastic.co/t/bulkprocessor-does-not-retry-on-failures/163945/2 "2019-02-08T18:11:40Z")

</div>

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