After allocating. node would have less than the required % free disk threshold (% free). preventing allocation – How to solve related issues

Average Read Time

2 Mins

After allocating. node would have less than the required % free disk threshold (% free). preventing allocation – 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 ” After allocating. node would have less than the required % free disk threshold (% free). preventing allocation ” 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 less than the required {}% free disk threshold ({}% free); preventing allocation” classname is DiskThresholdDecider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     node.nodeId(); freeBytesThresholdHigh; freeBytesAfterShard);
            return allocation.decision(Decision.NO; NAME; "after allocation less than required [%s] free on node; free: [%s]";
                    freeBytesThresholdLow; new ByteSizeValue(freeBytesAfterShard));
        }
        if (freeSpaceAfterShard 

 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content