Cluster health status changed from to reason: . – How to solve related issues

Cluster health status changed from to reason: . – 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 ” Cluster health status changed from to reason: . ” 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: allocation, cluster and routing.

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 (free tool that requires no installation).

Log Context

Log “Cluster health status changed from [{}] to [{}] (reason: [{}]).” classname is AllocationService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
    private void logClusterHealthStateChange(ClusterStateHealth previousStateHealth; ClusterStateHealth newStateHealth; String reason) {
        ClusterHealthStatus previousHealth = previousStateHealth.getStatus();
        ClusterHealthStatus currentHealth = newStateHealth.getStatus();
        if (!previousHealth.equals(currentHealth)) {
            logger.info("Cluster health status changed from [{}] to [{}] (reason: [{}])."; previousHealth; currentHealth; reason);
        }
    }

    private boolean hasDeadNodes(RoutingAllocation allocation) {
        for (RoutingNode routingNode : allocation.routingNodes()) {




 

Run the Check-Up to get a customized report like this:

Analyze your cluster