ConnectTransportException - failed to connect to discovered node on internal IP

183 views
Skip to first unread message

Peter-Paul Oldenzeel

unread,
Dec 1, 2014, 1:40:51 PM12/1/14
to elas...@googlegroups.com
We've implemented ElasticSearch in our PlayFramework app, and it's up and running (fast)!

We're having some trouble with discovering nodes. Our Java TransportClient can't seem to find extra nodes on the Qbox side, because it's using the internal IP to find them by:

[debug] o.e.c.transport - [Kiss] failed to connect to discovered node [[qbox-5471a94f71626f7756040000-p][wiIdQJyfRAacpwGyK0fyfA][ip-10-0-172-106][inet[/10.0.172.106:9300]]{max_local_storage_nodes=1}]

org.elasticsearch.transport.ConnectTransportException: [qbox-5471a94f71626f7756040000-p][inet[/10.0.172.106:9300]] connect_timeout[30s]

at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:718) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:647) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:615) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:129) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.client.transport.TransportClientNodesService$NodeSampler.validateNewNodes(TransportClientNodesService.java:317) [elasticsearch-1.1.0.jar:na]

Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.0.172.106:9300

at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) ~[elasticsearch-1.1.0.jar:na]

at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) ~[elasticsearch-1.1.0.jar:na]


Any idea how to get rid of this problem? 
Reply all
Reply to author
Forward
0 new messages