Hi, We have been seeing sporadic NodeDisconnectedException and NoNodeAvailableException in our ES cluster (0.90.7).
Our cluster is made up of 2 data nodes. One data node has a single primary shard and one data node has a single replica shard. We connect to using the Java TransportClient configured with both hosts. We're able to connect and index and query 98% of the time. I have played around with client.transport.ping_timeout and that seems to address our NoNodeAvailableException. However, we haven't been able to figure out the NodeDisconnectedException. 2014-03-21 12:53:18,322 DEBUG [ I/O worker #9}] [APP] > [.elasticsearch.transport.netty] [Pisces] *disconnected* from > [[#transport#-1][inet[prod-elasticsearch.domain/127.0.0.1:9300]]], *channel > closed event* > 2014-03-21 12:53:22,402 DEBUG [[generic][T#57]] [APP] > [.elasticsearch.transport.netty] [Pisces] *connected* to node > [[#transport#-1][inet[prod-elasticsearch.domain/127.0.0.1:9300]]] which is then immediately followed by: Caused by: org.elasticsearch.transport.*NodeDisconnectedException*: > [][inet[prod-elasticsearch.domain/127.0.0.1:9300]][index] *disconnected* These logs are all generated on the *client side* and there is nothing that sticks out in the logs on either of the nodes. I've seen in other posts that there might be network issues or that there might not be enough resources (cpu and/or memory). Does anyone have experience with these errors or know where I might want to be looking? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4494bbe9-e3f8-4069-a093-daa103e8f980%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
