# ClusterBlockException retries with Elasticsearch java client

**URL:** <https://discuss.elastic.co/t/clusterblockexception-retries-with-elasticsearch-java-client/89043>\
**Category:** Elasticsearch\
**Created:** [June 12, 2017, 1:04pm UTC](https://discuss.elastic.co/t/clusterblockexception-retries-with-elasticsearch-java-client/89043 "2017-06-12T13:04:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Davidovich](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Alex\_Davidovich](https://discuss.elastic.co/u/Alex_Davidovich)\
**Post date:** [June 12, 2017, 1:04pm UTC](https://discuss.elastic.co/t/clusterblockexception-retries-with-elasticsearch-java-client/89043/1 "2017-06-12T13:04:08Z")

</div>

I am trying to construct a retry mechanism when getting ClusterBlockException  
in case of master failover in Elasticsearch cluster.  
What should be the max timeout for this retry? When can I be positive that the cluster is down?

I encountered this issue and it's still open. No plans for fixing this?  
[open issue](https://github.com/elastic/elasticsearch/issues/11709)

---

<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 10, 2017, 1:04pm UTC](https://discuss.elastic.co/t/clusterblockexception-retries-with-elasticsearch-java-client/89043/2 "2017-07-10T13:04:11Z")

</div>

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