After allocating; node would have more than the allowed – How to solve related issues

Opster Team

Jan-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 ” After allocating; node would have more than the allowed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: allocation, cluster, node, routing and threshold.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “After allocating; node [{}] would have more than the allowed” classname is DiskThresholdDecider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 diskThresholdSettings.getHighWatermarkRaw();
                diskThresholdSettings.getFreeBytesThresholdHigh();
                freeBytesValue; new ByteSizeValue(shardSize));
        }
        if (freeSpaceAfterShard 

 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content