After allocating. node would have less than the required % free disk threshold (% free). preventing allocation – How To Solve Related Issues

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 try running the 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 

 

Optimize Elasticsearch Performance

Try The Tool