Nodes don't connect until keyboard interrupt is sent

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: [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at [netty-transport-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.util.concurrent.SingleThreadEventExecutor$ [netty-common-4.1.49.Final.jar:4.1.49.Final]
        at io.netty.util.internal.ThreadExecutorMap$ [netty-common-4.1.49.Final.jar:4.1.49.Final]
        at [?:?]

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).


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