Exception caught on netty layer

Elastic Stack Elasticsearch
1

hi, has anyone seen the below exception in ES log files.. im seeing this
and i dont know the reason why.. for the most part, things are working fine
though.

thanks

[2012-12-05 08:09:38,496][WARN ][transport.netty ] [Norrin Radd]
Exception caught on netty layer [[id: 0x79b2591c]]
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592)
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)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

--

2

Hello,

I guess there's a communication issue between your nodes. Which makes sense
in the context of your other thread (with the yellow and green status on
different nodes). As Ivan pointed out there, you probably ended up with two
clusters with the same name, even though you only intend to have one.

You can avoid this "split brain" situation if you set
zen.discovery.minimum_master_nodes to a value higher than half the total
number of master-eligible nodes in your cluster. Take a look here for
details:

Best regards,
Radu

http://sematext.com/ -- Elasticsearch -- Solr -- Lucene

On Wed, Dec 5, 2012 at 10:13 AM, T Vinod Gupta tvinod@readypulse.comwrote:

hi, has anyone seen the below exception in ES log files.. im seeing this
and i dont know the reason why.. for the most part, things are working fine
though.

thanks

[2012-12-05 08:09:38,496][WARN ][transport.netty ] [Norrin Radd]
Exception caught on netty layer [[id: 0x79b2591c]]
java.net.NoRouteToHostException: No route to host
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592)
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)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

--

--