I run some cronjobs that use the cluster stats api to retrieve the total cluster space and the current available cluster space in bytes and run some calculations on them. However, one of our clusters is now returning false values for those categories.
Over night our fs stats seem to have returned to normal. Very weird issue though, I'd be interested to hear if anyone else has experienced anything similar.
Update, this issue still exists. I had believed that it had resolved itself because I queried the cluster on another node and got back accurate values. However, it has become clear that this error is only happening on a single node.
These stats appear to be gathered locally then - what could be corrupted that could cause a result like this??
The nodes listing and the cluster summary come from two different APIs:
The node stats are literally the _nodes/stats API from Elasticsearch, per node, while the cluster summary is the _cluster/stats endpoint.
Something is weird making the _cluster/stats report so much data. I noticed in the picture that it says you have 4 nodes, but only 3 nodes appear? What is the 4th node?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.