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

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.

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 failed” classname is GatewayService.java.
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() {
                    
Override
                    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());
                    }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content