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

Average Read Time

2 Mins

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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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 customized insights on your system:

Analyze your cluster

Skip to content