# ElasticSearch retry vs failure exceptions

**URL:** <https://discuss.elastic.co/t/elasticsearch-retry-vs-failure-exceptions/35900>\
**Category:** Elasticsearch\
**Created:** [November 30, 2015, 1:42pm UTC](https://discuss.elastic.co/t/elasticsearch-retry-vs-failure-exceptions/35900 "2015-11-30T13:42:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike\_giardinelli](https://avatars.discourse-cdn.com/v4/letter/m/7ba0ec/32.png) [@mike\_giardinelli](https://discuss.elastic.co/u/mike_giardinelli)\
**Post date:** [November 30, 2015, 1:42pm UTC](https://discuss.elastic.co/t/elasticsearch-retry-vs-failure-exceptions/35900/1 "2015-11-30T13:42:23Z")

</div>

Which ElasticSearch (Java Transport Client) exceptions would be valid retry scenarios? By retry, I mean if encounter an error when writing a document or batch of documents to ES. The three obvious ones (at least seem obvious) are:

- NoNodeAvailableException
- ElasticsearchTimeoutException
- ReceiveTimeoutTransportException

For Failures (no retry) I have these two:

- ElasticsearchParseException
- ElasticsearchException

What other exceptions would be considered to be retry exceptions?

Any info is greatly appreciated. Thanks!

---

<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 5, 2017, 11:34pm UTC](https://discuss.elastic.co/t/elasticsearch-retry-vs-failure-exceptions/35900/2 "2017-07-05T23:34:51Z")

</div>