Failed to get size for – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.2

Briefly, this error occurs when Elasticsearch is unable to retrieve the size of a specific file or directory. This could be due to a number of reasons such as incorrect file permissions, the file or directory not existing, or a network issue. To resolve this issue, you can check if the file or directory exists and if Elasticsearch has the necessary permissions to access it. If it’s a network issue, ensure that Elasticsearch can communicate with the file or directory location. Also, check your Elasticsearch configuration to ensure it’s pointing to the correct path.

This guide will help you check for common problems that cause the log ” failed to get size for [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “failed to get size for [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            numDocs += readerContext.reader().numDocs();
            numDeletedDocs += readerContext.reader().numDeletedDocs();
            try {
                sizeInBytes += info.sizeInBytes();
            } catch (IOException e) {
                logger.trace(() -> new ParameterizedMessage("failed to get size for [{}]";; e);
        return new DocsStats(numDocs; numDeletedDocs; sizeInBytes);


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?