Upgrading to 1.0.1 is in the works.
There really isn't any useful information in the logs for the nodes from
what I can tell. I do see some of these TRACE logs:
[2014-03-22 14:08:20,732][TRACE][transport.netty ]
[prod-elasticsearch.domain] channel *closed*: [id: 0x2d18782f,
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
You should update your version to latest 0.90.x version or 1.0.1 although it
probably won't solve your network issue.
I suppose you don't have anything in nodes logs?
How much HEAP did you give to your nodes?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 21 mars 2014 à
