Log Recovery failed – How To Solve Related Issues

Log Recovery failed – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Recovery failed” it’s important to understand a few problems related to Elasticsearch concepts recovery. See bellow important tips and explanations on these concepts

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());
                    }




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Failing to start shard in ElasticSearch IndexShardGatewayRecoveryException “sending failed”

13.09 K 9

Failed Shard Recovery  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now