Opster Team

Feb-20, Version: 1.7-8.0

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

                     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