Failed to check index – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

Briefly, this error message indicates that Elasticsearch was unable to check an index. The reason for this error could be a corrupt index or a problem with the Elasticsearch instance. To resolve the issue, the index can be deleted and recreated or Elasticsearch can be restarted.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Failed to check index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and shard.

Log Context

Log “failed to check index” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     logger.debug("check index [success]\n{}"; new String(os.bytes().toBytes(); Charsets.UTF_8));
            recoveryState.getStart().checkIndexTime(Math.max(0; TimeValue.nsecToMSec(System.nanoTime() - timeNS)));
        } catch (Exception e) {
            logger.warn("failed to check index"; e);

    public Engine engine() {
        Engine engine = engineUnsafe();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content