Updating cluster.routing.allocation.node_concurrent_recoveries – How to solve related issues

Average Read Time

2 Mins

Updating cluster.routing.allocation.node_concurrent_recoveries – How to solve related issues

Opster Team

Feb-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 ” Updating cluster.routing.allocation.node_concurrent_recoveries ” 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 “updating [cluster.routing.allocation.node_concurrent_recoveries] from [{}] to [{}]” classname is ThrottlingAllocationDecider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 ThrottlingAllocationDecider.this.primariesInitialRecoveries = primariesInitialRecoveries;

            int concurrentRecoveries = settings.getAsInt(CLUSTER_ROUTING_ALLOCATION_NODE_CONCURRENT_RECOVERIES; ThrottlingAllocationDecider.this.concurrentRecoveries);
            if (concurrentRecoveries != ThrottlingAllocationDecider.this.concurrentRecoveries) {
                logger.info("updating [cluster.routing.allocation.node_concurrent_recoveries] from [{}] to [{}]"; ThrottlingAllocationDecider.this.concurrentRecoveries; concurrentRecoveries);
                ThrottlingAllocationDecider.this.concurrentRecoveries = concurrentRecoveries;


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

Analyze your cluster