NoRouteToHostException when one of the ES instance rebuild in cluster

could you please reply with fix for below error

ES version 2.1

code to connect to ES
final Settings settings = Settings.settingsBuilder().put("", clusterName).put("client.transport.sniff", true).build();
client = TransportClient.builder().settings(settings).addPlugin(DeleteByQueryPlugin.class).build();
InetSocketTransportAddress iNetSocketTransportAddressForEsHost = new InetSocketTransportAddress(iNetAddressForEsHost, port);


2017-03-13 23:09:51.793 o.e.t.netty [WARN] [Fever Pitch] exception caught on transport layer [[id: 0x8e7656a3]], closing connection No route to host
at Method) ~[?:1.7.0_131]
at ~[?:1.7.0_131]
at ~[stormjar.jar:?]
at [stormjar.jar:?]
at [stormjar.jar:?]
at [stormjar.jar:?]
at [stormjar.jar:?]
at [stormjar.jar:?]
at org.jboss.netty.util.internal.DeadLockProofWorker$ [stormjar.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.7.0_131]
at java.util.concurrent.ThreadPoolExecutor$ [?:1.7.0_131]
at [?:1.7.0_131]

For some reason the client cannot connect to ES. No route to host is not an ES problem, but an OS one.

Can you ping the node?

Thanks for reply . Yes I can ping node. But the exception is happening continuously . ES cluster is green.

I see so many users posted this issue but I didnt find any solution.

Thanks for reply, y
es I'm able to ping and when I do nslookup on hostname IP address is

I was told that this issue will be addressed since ES 5.1 ; there is no workaround solution for other scenarios. only way is to rebuild the dependent ES client applications to re-establish with ES nodes.

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