How To Solve Issues Related to Log – Rerouting shards:

How To Solve Issues Related to Log – Rerouting shards:

Updated: Jan-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 “Rerouting shards:” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, monitor, routing, threshold. See bellow important tips and explanations on these concepts

Log Context

Log”Rerouting shards: [{}]” classname is DiskThresholdMonitor.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         }
                    }
                }
            }
            if (reroute) {
                logger.info("rerouting shards: [{}]"; explanation);
                reroute();
            }
            indicesToMarkReadOnly.removeIf(index -> state.getBlocks().indexBlocked(ClusterBlockLevel.WRITE; index));
            if (indicesToMarkReadOnly.isEmpty() == false) {
                markIndicesReadOnly(indicesToMarkReadOnly);




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 ElasticSearch: Unassigned Shards, how to fix?

203.11 K 152

Rerouting Shards In Cluster  

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