Opster Team
Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.
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.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.
Log Context
Log “Failed to fetch fs stats – returning empty instance” classname is FsService.java.
We extracted the following from Elasticsearch source code for those seeking 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(); } } }
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Try FreeConnect in under 3 minutes
Adam Bregenzer
CTO at Groupsense