# Failed to connect to node \[..\], removed from node list **URL:** \ **Category:** Elasticsearch\ **Created:** [January 26, 2012, 2:01pm UTC](https://discuss.elastic.co/t/failed-to-connect-to-node-removed-from-node-list/6512 "2012-01-26T14:01:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![maik](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@maik](https://discuss.elastic.co/u/maik)\ **Post date:** [January 26, 2012, 2:01pm UTC](https://discuss.elastic.co/t/failed-to-connect-to-node-removed-from-node-list/6512/1 "2012-01-26T14:01:53Z")
Hi, I'm just testing elasticsearch clusters and how to handle node-downtimes in the application. I'm on version 0.18.6, two nodes on the same local machine. Everything works fine tough, searching, filtering etc. Shutting down one node (does not matter which), with strg+c causes the application to log the following message: 2012-01-26 14:51:37: [org.elasticsearch.client.transport] - [Mother Night] Failed to connect to node [#transport#-1][inet[/10.1.1.2:9300]], removed from nodes list org.elasticsearch.transport.ConnectTransportException: [][inet[/10.1.1.2:9300]] connect\_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:124) at org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler.sample(TransportClientNodesService.java:262) at org.elasticsearch.client.transport.TransportClientNodesService$ScheduledNodeSampler.run(TransportClientNodesService.java:245) 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:680) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370) at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) ... 3 more In the first moment I thought "Fine, node is automatically removed from the node list. Nothing to do for me". The problem: The application logs this message every 5 Seconds. Is there a method to remove the node temporary, so this message does not appear so often? How is the usually way to handle such failures? Perhaps I want to shut the machine down forever, how do I do it, without lots of errormessages? Thx in advance Greetings Maik ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 27, 2012, 8:38pm UTC](https://discuss.elastic.co/t/failed-to-connect-to-node-removed-from-node-list/6512/2 "2012-01-27T20:38:16Z")
You are using the TransportClient, and you added that node as an address to be connected to. So, it will try to re-establish the connection to that node. The logging is in DEBUG level, so you can reduce the logging level in your app. On Thursday, January 26, 2012 at 4:01 PM, maik wrote: > Hi, > > I'm just testing elasticsearch clusters and how to handle node-downtimes in the application. > > I'm on version 0.18.6, two nodes on the same local machine. > Everything works fine tough, searching, filtering etc. > > Shutting down one node (does not matter which), with strg+c causes the application to log the following message: > > 2012-01-26 14:51:37: [org.elasticsearch.client.transport] - [Mother Night] Failed to connect to node [#transport#-1][inet[/10.1.1.2:9300]], removed from nodes list > org.elasticsearch.transport.ConnectTransportException: [inet[/10.1.1.2:9300]] connect\_timeout[30s] > at org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:560) > at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:503) > at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:482) > at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:124) > at org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler.sample(TransportClientNodesService.java:262) > at org.elasticsearch.client.transport.TransportClientNodesService$ScheduledNodeSampler.run(TransportClientNodesService.java:245) > 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:680) > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567) > at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401) > at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370) > at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292) > at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) > ... 3 more > > In the first moment I thought "Fine, node is automatically removed from the node list. Nothing to do for me". > The problem: The application logs this message every 5 Seconds. > > Is there a method to remove the node temporary, so this message does not appear so often? > How is the usually way to handle such failures? > Perhaps I want to shut the machine down forever, how do I do it, without lots of errormessages? > > Thx in advance > Greetings > Maik ---
**Author:** ![maik](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@maik](https://discuss.elastic.co/u/maik)\ **Post date:** [February 7, 2012, 6:54am UTC](https://discuss.elastic.co/t/failed-to-connect-to-node-removed-from-node-list/6512/3 "2012-02-07T06:54:35Z")
Thx kimchy (was away for some days, so i could not thank you earlier :D) ---
**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:40am UTC](https://discuss.elastic.co/t/failed-to-connect-to-node-removed-from-node-list/6512/4 "2017-07-06T03:40:24Z")