# Retryable exceptions in elasticsearch

**URL:** <https://discuss.elastic.co/t/retryable-exceptions-in-elasticsearch/107312>\
**Category:** Elasticsearch\
**Created:** [November 12, 2017, 5:03pm UTC](https://discuss.elastic.co/t/retryable-exceptions-in-elasticsearch/107312 "2017-11-12T17:03:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ckant](https://avatars.discourse-cdn.com/v4/letter/c/dc4da7/32.png) [@ckant](https://discuss.elastic.co/u/ckant)\
**Post date:** [November 12, 2017, 5:03pm UTC](https://discuss.elastic.co/t/retryable-exceptions-in-elasticsearch/107312/1 "2017-11-12T17:03:06Z")

</div>

Hi,  
Elasticsearch can throw exceptions for many reasons. I want to retry on those failures that are intermittent like network failure because I dont want my to let my pipeline redo the whole computation just because there was a network blip. I looked at elasticsearch exceptions , but there are so many of them with little or next to none documentation. Can somebody help me in categorizing exceptions on which I can wait for couple for couple of seconds and then retry. ConnectTransportException seems like a candidate. NoNodeAvailableException also seems plausible. I am connecting through Transportclient in java

Thanks  
ckant

---

<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:** [December 10, 2017, 5:03pm UTC](https://discuss.elastic.co/t/retryable-exceptions-in-elasticsearch/107312/2 "2017-12-10T17:03:12Z")

</div>

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