# Trouble with TransportClient through ELB in front of 2-node cluster: getting NoNodeAvailableException and NodeDisconnectedException **URL:** \ **Category:** Elasticsearch\ **Created:** [May 29, 2013, 2:34am UTC](https://discuss.elastic.co/t/trouble-with-transportclient-through-elb-in-front-of-2-node-cluster-getting-nonodeavailableexception-and-nodedisconnectedexception/12161 "2013-05-29T02:34:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![george\_monroe](https://avatars.discourse-cdn.com/v4/letter/g/bbce88/32.png) [@george\_monroe](https://discuss.elastic.co/u/george_monroe)\ **Post date:** [May 29, 2013, 2:34am UTC](https://discuss.elastic.co/t/trouble-with-transportclient-through-elb-in-front-of-2-node-cluster-getting-nonodeavailableexception-and-nodedisconnectedexception/12161/1 "2013-05-29T02:34:46Z")
We've been seeing mysterious issues with the TransportClient running against ES 0.20.5. We have an AWS ELB in front of 2-node cluster. Only the ELB hostname is added to the client startup without sniffing, and we are setting elasticsearchSettings.put("client.transport.ping\_timeout", "60s"), which is quite a lot if you ask me. But, still seeing TransportClient issues. The NoNodeAvailableException due to timing out, we put a bandaid on by setting the ping\_timeout to 60s... But the latest exception is simply NodeDisconnectedException. All of this is happening in PROD, so we're trying to resolve this as timely as possible. Would really appreciate any ideas. So far, I think the AWS ELB might be the problem, but removing TransportClient and using something like JEST is also on the table. Please pitch in ideas! LATEST: Caused by: org.elasticsearch.transport.NodeDisconnectedException: [][inet[ [internal-ocho-prodB-elasticsearch-234234234.us-west-2.elb.amazonaws.com/XX.X.X.XXX:9300](http://internal-ocho-prodB-elasticsearch-234234234.us-west-2.elb.amazonaws.com/XX.X.X.XXX:9300)]][indices/refresh[http://internal-ocho-prodb-elasticsearch-993270121.us-west-2.elb.amazonaws.com/10.0.0.235:9300]][indices/refresh](http://internal-ocho-prodb-elasticsearch-993270121.us-west-2.elb.amazonaws.com/10.0.0.235:9300%5D%5D%5Bindices/refresh)] disconnected EARLY-ON HEADACHE (Why would 5 seconds not be enough???) : 2013-05-01 17:04:13.344 [elasticsearch[John Walker][generic][T#1]] INFO org.elasticsearch.client.transport - [John Walker] failed to get node info for [#transport#-1][inet[ [ocho-prdB-elasticsearch01.us-west-2b.XXXXXXXXXXXXXXXXX.com/:9300](http://ocho-prdB-elasticsearch01.us-west-2b.XXXXXXXXXXXXXXXXX.com/:9300)][http://ocho-prdb-elasticsearch01.us-west-2b.demandforce.com/10.0.1.72:9300]](http://ocho-prdb-elasticsearch01.us-west-2b.demandforce.com/10.0.1.72:9300%5D)], disconnecting... org.elasticsearch.transport.ReceiveTimeoutTransportException: [][inet[ [ocho-prdB-elasticsearch01XXXXXXXXXXXXXX.com/:9300](http://ocho-prdB-elasticsearch01XXXXXXXXXXXXXX.com/:9300)]][cluster/nodes/info[http://ocho-prdb-elasticsearch01.us-west-2b.demandforce.com/10.0.1.72:9300]][cluster/nodes/info](http://ocho-prdb-elasticsearch01.us-west-2b.demandforce.com/10.0.1.72:9300%5D%5D%5Bcluster/nodes/info)] request\_id [38904] timed out after [5013ms] at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342) ~[es-migration-1.8.178.jar:?] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [?:1.6.0\_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [?:1.6.0\_33] at java.lang.Thread.run(Thread.java:662) [?:1.6.0\_33] Exception in thread "main" org.elasticsearch.client.transport.NoNodeAvailableException: No node available at org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:246) at org.elasticsearch.action.TransportActionNodeProxy$1.handleException(TransportActionNodeProxy.java:84) at org.elasticsearch.transport.TransportService$Adapter$2$1.run(TransportService.java:305) 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) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:34am UTC](https://discuss.elastic.co/t/trouble-with-transportclient-through-elb-in-front-of-2-node-cluster-getting-nonodeavailableexception-and-nodedisconnectedexception/12161/2 "2017-07-06T02:34:15Z")