Node did not return any filesystem stats – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.12-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve filesystem statistics from a node. This could be due to insufficient permissions, a misconfigured Elasticsearch setup, or an issue with the underlying filesystem. To resolve this, you can check the Elasticsearch logs for more detailed error messages. Ensure that Elasticsearch has the necessary permissions to access the filesystem. Also, verify your Elasticsearch configuration, particularly settings related to and path.logs. If the issue persists, investigate potential problems with the underlying filesystem.

This guide will help you check for common problems that cause the log ” node [{}/{}] did not return any filesystem stats ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, node.

Log Context

Log “node [{}/{}] did not return any filesystem stats” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     * file system data in the NodeStats or if the total bytes are a negative number.
    public static DiskUsage findLeastAvailablePath(NodeStats nodeStats) {
        if (nodeStats.getFs() == null) {
            logger.warn("node [{}/{}] did not return any filesystem stats"; nodeStats.getNode().getName(); nodeStats.getNode().getId());
            return null;

        FsInfo.Path leastAvailablePath = null;
        for (FsInfo.Path info : nodeStats.getFs()) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?