# TransportClient node failures

**URL:** <https://discuss.elastic.co/t/transportclient-node-failures/115347>\
**Category:** Elasticsearch\
**Created:** [January 12, 2018, 6:05pm UTC](https://discuss.elastic.co/t/transportclient-node-failures/115347 "2018-01-12T18:05:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashokm](https://avatars.discourse-cdn.com/v4/letter/a/ecae2f/32.png) [@ashokm](https://discuss.elastic.co/u/ashokm)\
**Post date:** [January 12, 2018, 6:05pm UTC](https://discuss.elastic.co/t/transportclient-node-failures/115347/1 "2018-01-12T18:05:12Z")

</div>

We are on ES 2.4 with 5 Nodes. We are creating 1 replica for all indices. We are using transport client to connect to cluster for search and Index operations. When one of the nodes go down, we are getting various errors and I am wondering how clients are expected to deal with these issue. Errors we are seeing are

1. java.util.concurrent.ExecutionException: ClusterBlockException[blocked by: [SERVICE\_UNAVAILABLE/2/no master];  
We have 3 eligible master nodes and when master nodes and within seconds another node becomes master but we still get the above error
2. Scroll Not available
3. [SERVICE\_UNAVAILABLE/1/state not recovered / initialized]

Any help on how client code should be updated to handle these scenarios is greatly appreciated

---

<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 9, 2018, 6:05pm UTC](https://discuss.elastic.co/t/transportclient-node-failures/115347/2 "2018-02-09T18:05:34Z")

</div>

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