Product
Knowledge Center
Company
ES Check-Up

How To Solve Issues Related to Log – Failed to fetch fs stats returning empty instance

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Failed to fetch fs stats returning empty instance” it’s important to understand common problems related to Elasticsearch concepts: monitor. See detailed explanations below complete with common problems, examples and useful tips.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 ElasticSearch find disk space usage 52.25 K ✔51

2Github Issue Number 18279  

Log Context

Log ”Failed to fetch fs stats – returning empty instance” classname is FsService.java
We have extracted the following from Elasticsearch source code to get an in-depth context : 

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

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster