How To Solve Issues Related to Log – After allocating; node would have more than the allowed

How To Solve Issues Related to Log – After allocating; node would have more than the allowed

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 more than the allowed” 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” 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 < diskThresholdSettings.getFreeDiskThresholdHigh()) {
            logger.warn("after allocating; node [{}] would have more than the allowed " +
                            "{} free disk threshold ({} free); preventing allocation";
                    node.nodeId(); Strings.format1Decimals(diskThresholdSettings.getFreeDiskThresholdHigh(); "%");
                                                           Strings.format1Decimals(freeSpaceAfterShard; "%"));
            return allocation.decision(Decision.NO; NAME;
                "allocating the shard to this node will bring the node above the high watermark cluster setting [%s=%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 low disk watermark [??%] exceeded on 54.99 K 55

Elasticsearch Disk Space Issues after Close   0.73 K 2

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