Recovery failed – How to solve related issues

Opster Team

Jan-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 the recovery process for an index has failed. The recovery process is usually triggered when a node in the Elasticsearch cluster is restarted or when a shard is relocated to a new node. If the recovery process fails, it could be due to various reasons such as network issues, hardware failures, or corruption of the index. To resolve this issue, you can try restarting the recovery process or running the index recovery process manually. Additionally, you should investigate the root cause of the recovery failure and take the necessary steps to address the underlying issue.

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. Take a self-guided product tour to see for yourself (no registration required).

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

Log Context

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

         } else {
            if (recovered.compareAndSet(false; true)) {
                threadPool.generic().execute(new AbstractRunnable() {
                    public void onFailure(Exception e) {
                        logger.warn("Recovery failed"; e);
                        // we reset `recovered` in the listener don't reset it here otherwise there might be a race
                        // that resets it to false while a new recover is already running?
                        recoveryListener.onFailure("state recovery failed: " + e.getMessage());


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content