Log Updating cluster.routing.allocation.cluster-concurrent-rebalance from ; to – How To Solve Related Issues



Log Updating cluster.routing.allocation.cluster-concurrent-rebalance from ; to – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

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 “Updating cluster.routing.allocation.cluster-concurrent-rebalance from ; to” 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, rebalance, 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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log “updating [cluster.routing.allocation.cluster_concurrent_rebalance] from [{}]; to [{}]” classname is ConcurrentRebalanceAllocationDecider.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     class ApplySettings implements NodeSettingsService.Listener {
        
Override
        public void onRefreshSettings(Settings settings) {
            int clusterConcurrentRebalance = settings.getAsInt(CLUSTER_ROUTING_ALLOCATION_CLUSTER_CONCURRENT_REBALANCE; ConcurrentRebalanceAllocationDecider.this.clusterConcurrentRebalance);
            if (clusterConcurrentRebalance != ConcurrentRebalanceAllocationDecider.this.clusterConcurrentRebalance) {
                logger.info("updating [cluster.routing.allocation.cluster_concurrent_rebalance] from [{}]; to [{}]"; ConcurrentRebalanceAllocationDecider.this.clusterConcurrentRebalance; clusterConcurrentRebalance);
                ConcurrentRebalanceAllocationDecider.this.clusterConcurrentRebalance = clusterConcurrentRebalance;
            }
        }
    }









Find Configuration Errors

Try The Tool