# Cluster cannot resume automatically after the last member timeout

**URL:** <https://discuss.elastic.co/t/cluster-cannot-resume-automatically-after-the-last-member-timeout/8096>\
**Category:** Elasticsearch\
**Created:** [June 14, 2012, 2:40am UTC](https://discuss.elastic.co/t/cluster-cannot-resume-automatically-after-the-last-member-timeout/8096 "2012-06-14T02:40:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ywtsang](https://avatars.discourse-cdn.com/v4/letter/y/a698b9/32.png) [@ywtsang](https://discuss.elastic.co/u/ywtsang)\
**Post date:** [June 14, 2012, 2:40am UTC](https://discuss.elastic.co/t/cluster-cannot-resume-automatically-after-the-last-member-timeout/8096/1 "2012-06-14T02:40:53Z")

</div>

I have 2 node cluster and 1 java process running the redexing jobs for  
every minute using TransportClient.

1. I take down 1 node, and the client can fail over and continue to  
work without problem

2. suddenly the client have timeout to get local cluster state and  
exception is thrown:

2012-06-13 18:06:39,630 INFO org.elasticsearch.client.transport - [Rick Jones] failed to get local cluster state for [Klaw][NJ8o2F7dQ0eg1JO97b1W0w][inet[/10.1.4.197:9300]], disconnecting... org.elasticsearch.transport.ReceiveTimeoutTransportException: [Klaw][inet[/10.1.4.197:9300]][cluster/state] request\_id [46533] timed out after [5001ms] at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:347) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
1. and from all the subsequent index requests submitted by the  
TransportClient, exception "No node available" is thrown and it cannot  
recover by itself even the node is still there and up.

2. when I bring the downed node (the one taken down in step 1), the  
TransportClient can detect and resume to conncet to the cluster

Does that mean the TransportClient will not resume when the last  
member of the cluster "timeout"?

Wing

---

<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 6, 2017, 3:24am UTC](https://discuss.elastic.co/t/cluster-cannot-resume-automatically-after-the-last-member-timeout/8096/2 "2017-07-06T03:24:19Z")

</div>

Closed on July 6, 2017, 3:24am UTC