Rerouting because disk usage info received from new nodes – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.1-8.9

Briefly, this error occurs when Elasticsearch receives disk usage information from new nodes and determines that the current routing of shards is not optimal. This could be due to the new nodes having more available disk space, causing Elasticsearch to reroute shards to balance disk usage across the cluster. To resolve this, you can manually control the shard allocation using the cluster reroute API, or adjust the disk-based shard allocation settings to better suit your cluster’s needs. Also, ensure that all nodes in the cluster have sufficient disk space to prevent unnecessary rerouting.

This guide will help you check for common problems that cause the log ” rerouting because disk usage info received from new nodes ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: routing, allocation, cluster.

Log Context

Log “rerouting because disk usage info received from new nodes” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        cleanUpRemovedNodes(nodes; nodesOverHighThreshold);
        cleanUpRemovedNodes(nodes; nodesOverHighThresholdAndRelocating);

        if (lastNodes.equals(nodes) == false) {
            if (lastNodes.containsAll(nodes) == false) {
                logger.debug("rerouting because disk usage info received from new nodes");
                reroute = true;
            lastNodes = Collections.unmodifiableSet(nodes);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?