Recovery from failed – 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 can resolve issues that cause many errors.

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

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 “[{}][{}] recovery from [{}] failed” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 if (cause instanceof AlreadyClosedException) {
                    listener.onIgnoreRecovery(true; "source shard is closed (" + request.sourceNode() + ")");

                logger.warn("[{}][{}] recovery from [{}] failed"; e; request.shardId().index().name(); request.shardId().id(); request.sourceNode());
                listener.onRecoveryFailure(new RecoveryFailedException(request; e); true);
            } finally {
        } else {


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content