Failed to fetch fs stats – returning empty instance – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to fetch file system statistics, possibly due to insufficient permissions or a misconfigured path. To resolve this issue, you can try the following: 1) Check and adjust the permissions of the Elasticsearch directories to ensure the Elasticsearch process can access them. 2) Verify the path settings in your Elasticsearch configuration to ensure they are correct. 3) Check the health of your file system, as this error can also occur if there are issues with the file system itself.

This guide will help you check for common problems that cause the log ” Failed to fetch fs stats – returning empty instance ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: monitor.

Log Context

Log “Failed to fetch fs stats – returning empty instance” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        protected FsInfo refresh() {
            try {
                return probe.stats();
            } catch (IOException ex) {
                logger.warn("Failed to fetch fs stats - returning empty instance");
                return new FsInfo();


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?