Updated: Jan-20
Elasticsearch Version: 1.7-8.0Background
Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.
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 ✔9About Opster
Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance
