Failed to read latest segment infos on flush – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to read the latest segment information during a flush operation. This could be due to issues like disk I/O errors, insufficient disk space, or corrupted index files. To resolve this issue, you can try the following: 1) Check and free up disk space if necessary. 2) Check for any hardware or OS level issues causing disk I/O errors. 3) Try to restore the index from a backup. 4) If the index is not critical, consider deleting and recreating it.

This guide will help you check for common problems that cause the log ” failed to read latest segment infos on flush ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, flush.

Log Context

Log “failed to read latest segment infos on flush” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        try {
            // reread the last committed segment infos
            lastCommittedSegmentInfos = store.readLastCommittedSegmentsInfo();
        } catch (Exception e) {
            if (isClosed.get() == false) {
                logger.warn("failed to read latest segment infos on flush"; e);
                if (Lucene.isCorruptionException(e)) {
                    throw new FlushFailedEngineException(shardId; e);
        } finally {


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?