How To Solve Issues Related to Log – After allocating; node would have less than the required threshold of

How To Solve Issues Related to Log – After allocating; node would have less than the required threshold of

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “After allocating; node would have less than the required threshold of” 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 less than the required threshold of” classname is DiskThresholdDecider.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         final long shardSize = getExpectedShardSize(shardRouting; allocation; 0);
        assert shardSize >= 0 : shardSize;
        double freeSpaceAfterShard = freeDiskPercentageAfterShardAssigned(usage; shardSize);
        long freeBytesAfterShard = freeBytes - shardSize;
        if (freeBytesAfterShard < diskThresholdSettings.getFreeBytesThresholdHigh().getBytes()) {
            logger.warn("after allocating; node [{}] would have less than the required threshold of " +
                    "{} free (currently {} free; estimated shard size is {}); preventing allocation";
                    node.nodeId(); diskThresholdSettings.getFreeBytesThresholdHigh(); freeBytesValue; new ByteSizeValue(shardSize));
            return allocation.decision(Decision.NO; NAME;
                "allocating the shard to this node will bring the node above the high watermark cluster setting [%s=%s] " +
                    "and cause it to have less than the minimum required [%s] of free space (free: [%s]; estimated shard size: [%s])";




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 Elasticsearch Disk Space Issues after Close 0.73 K 2

Low Disk Watermark 15 Exceeded On  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now