I notice a strange behavior on the ES cluster today. Our developers attach
5 client nodes on our 5 nodes (all have data) ES cluster. While client
nodes were operetional i remove a data node from the cluster to test the
overhead. When cluster got green our developers stopped all the client
nodes and our ES cluster crushed. We manage to recover it with a full
restart. You may see the error below, somehow all nodes lost each-other.
Any idea why that may happen? Thank you!
[2013-07-10 16:40:56,827][WARN ][discovery.zen.ping.multicast]
[K44ES_node_03] failed to connect to requesting node [K44ES_node_05][vKP5F
05eSEWHX8NvLm9CwQ][inet[/10.128.36.26:9300]]
org.elasticsearch.transport.ConnectTransportException:
[K44ES_node_05][inet[/10.128.36.26:9300]] connect_timeout[30s]
at
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:671)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:610)
at
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:580)
at
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:127)
at
org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver$2.run(MulticastZenPing.java:539)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.