Cluster info unavailable for disk threshold decider allowing allocation – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.1

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch cannot retrieve cluster information to make disk allocation decisions. This could be due to network issues, node failures, or misconfigurations. To resolve this, ensure all nodes are properly connected and communicating. Check your cluster health and configuration settings. If a node is down, bring it back up. If there’s a network issue, resolve it to restore communication. Lastly, ensure that the disk-based shard allocation settings are correctly configured.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” cluster info unavailable for disk threshold decider; allowing allocation. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: threshold, cluster, allocation, routing.

Log Context

Log “cluster info unavailable for disk threshold decider; allowing allocation.” classname is DiskThresholdDecider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // Fail open there is no info available
        final ClusterInfo clusterInfo = allocation.clusterInfo();
        if (clusterInfo == null) {
            if (logger.isTraceEnabled()) {
                logger.trace("cluster info unavailable for disk threshold decider; allowing allocation.");
            }
            return allocation.decision(Decision.YES; NAME; "the cluster info is unavailable");
        }

        // Fail open if there are no disk usages available

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?