Log After allocating; node would have more than the allowed free disk threshold ( free); preventing allocation – How To Solve Related Issues

Log After allocating; node would have more than the allowed free disk threshold ( free); preventing allocation – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “After allocating; node would have more than the allowed free disk threshold ( free); preventing allocation” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, node, routing, threshold. See bellow important tips and explanations on these concepts

Log Context

Log”after allocating; node [{}] would have more than the allowed {} 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 



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 low disk watermark [??%] exceeded on

54.99 K 55

Elasticsearch Disk Space Issues after Close

  0.73 K 2

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now