Recovery from failed – How to solve related issues

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[{}][{}] recovery from [{}] failed” classname is RecoveryTarget.java
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() + ")");
                    return;
                }

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




 

Run the Check-Up to get a customized report like this:

Analyze your cluster