How To Solve Issues Related to Log – Updating cluster.routing.allocation.node_initial_primaries_recoveries from to

How To Solve Issues Related to Log – Updating cluster.routing.allocation.node_initial_primaries_recoveries from to

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Updating cluster.routing.allocation.node_initial_primaries_recoveries from to” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, routing. See bellow important tips and explanations on these concepts

Log Context

Log”updating [cluster.routing.allocation.node_initial_primaries_recoveries] from [{}] to [{}]” classname is ThrottlingAllocationDecider.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 primariesInitialRecoveries = settings.getAsInt(CLUSTER_ROUTING_ALLOCATION_NODE_INITIAL_PRIMARIES_RECOVERIES; ThrottlingAllocationDecider.this.primariesInitialRecoveries);
            if (primariesInitialRecoveries != ThrottlingAllocationDecider.this.primariesInitialRecoveries) {
                logger.info("updating [cluster.routing.allocation.node_initial_primaries_recoveries] from [{}] to [{}]"; ThrottlingAllocationDecider.this.primariesInitialRecoveries; primariesInitialRecoveries);
                ThrottlingAllocationDecider.this.primariesInitialRecoveries = primariesInitialRecoveries;
            }

            int concurrentRecoveries = settings.getAsInt(CLUSTER_ROUTING_ALLOCATION_NODE_CONCURRENT_RECOVERIES; ThrottlingAllocationDecider.this.concurrentRecoveries);
            if (concurrentRecoveries != ThrottlingAllocationDecider.this.concurrentRecoveries) {



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Solved Improving Snapshot Recovery  

Github Issue Number 14387  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now