Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues causing many log errors (free and no installation required)
This guide will help you check for common problems that cause the log “Recovered indices into cluster-state” 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: 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 discover the cause of many errors and provides suitable actionable recommendations.
Log Context
Log”recovered [{}] indices into cluster_state” classname is GatewayService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
GatewayRecoveryListener.this.onFailure("failed to updated cluster state");
}
Override
public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {
logger.info("recovered [{}] indices into cluster_state"; newState.metaData().indices().size());
}
});
}
Override
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 Elasticsearch doesn’t respond after index recovering -views 3.97 K ,score 4
2 Failed to start Sonar Webservice -views 5.51 K,score 9
About Opster
Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.
