Unable to retrieve node FS stats for (version 6.8) – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Unable to retrieve node FS stats for (version 6.8) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and node.

Log Context

Log “Unable to retrieve node FS stats for {}” classname is InternalClusterInfoService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     static void fillDiskUsagePerNode(Logger logger; List nodeStatsArray;
            ImmutableOpenMap.Builder newLeastAvaiableUsages;
            ImmutableOpenMap.Builder newMostAvaiableUsages) {
        for (NodeStats nodeStats : nodeStatsArray) {
            if (nodeStats.getFs() == null) {
                logger.warn("Unable to retrieve node FS stats for {}"; nodeStats.getNode().getName());
            } else {
                FsInfo.Path leastAvailablePath = null;
                FsInfo.Path mostAvailablePath = null;
                for (FsInfo.Path info : nodeStats.getFs()) {
                    if (leastAvailablePath == null) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content