# Nodes don't connect until keyboard interrupt is sent

**URL:** <https://discuss.elastic.co/t/nodes-dont-connect-until-keyboard-interrupt-is-sent/240125>\
**Category:** Elasticsearch\
**Created:** [July 7, 2020, 9:02am UTC](https://discuss.elastic.co/t/nodes-dont-connect-until-keyboard-interrupt-is-sent/240125 "2020-07-07T09:02:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![defalt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/defalt/32/71379_2.png) [@defalt](https://discuss.elastic.co/u/defalt)\
**Post date:** [July 7, 2020, 9:02am UTC](https://discuss.elastic.co/t/nodes-dont-connect-until-keyboard-interrupt-is-sent/240125/1 "2020-07-07T09:02:21Z")

</div>

Hi,  
I have a cluster of 3 nodes. I had the problem that I turned off one node and when I turned in back on it didn't connect until I sent a keyboard interrupt (CTRL+C) in the terminal on a second node. After that they shook hands and connected.  
Is this **error** just **common** when you **run** it **over** the **terminal**? Is it **prevented** when I run it as a **service**?  
Error on the node:

```auto
tractNioByteChannel.java:163) [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:615) [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:578) [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-common-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.49.Final.jar:4.1.49.Final]
        at java.lang.Thread.run(Thread.java:832) [?:?]

```

It looks like elasticsearch is not refreshing until I send an interrupt.  
It occured to me many times in the last few weeks and this shouldn't happen in a working environment (my cluster is just for experimenting right now but should go into production in a few weeks).

Thanks,  
_defalt_

---

<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:** [August 4, 2020, 9:02am UTC](https://discuss.elastic.co/t/nodes-dont-connect-until-keyboard-interrupt-is-sent/240125/2 "2020-08-04T09:02:21Z")

</div>

Closed on August 4, 2020, 9:02am UTC

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