Failed to gather node load limits failure Returning no scale – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-8.9

Briefly, this error occurs when Elasticsearch fails to gather the load limits of a node, which is crucial for scaling operations. This could be due to network issues, node unavailability, or insufficient permissions. To resolve this, ensure that all nodes are up and running, check network connectivity, and verify that Elasticsearch has the necessary permissions to gather node load limits. Additionally, check your cluster’s health and configuration settings. If the issue persists, consider increasing the timeout settings or scaling your cluster manually.

This guide will help you check for common problems that cause the log ” [{}] failed to gather node load limits; failure [{}]. Returning no scale ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node.

Log Context

Log “[{}] failed to gather node load limits; failure [{}]. Returning no scale” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        List nodeLoads = new ArrayList(mlContext.mlNodes.size());
        boolean nodeLoadIsMemoryAccurate = true;
        for (DiscoveryNode node : mlContext.mlNodes) {
            NodeLoad nodeLoad = nodeLoadDetector.detectNodeLoad(clusterState; node; maxOpenJobs; maxMachineMemoryPercent; useAuto);
            if (nodeLoad.getError() != null) {
                logger.warn("[{}] failed to gather node load limits; failure [{}]. Returning no scale"; node.getId(); nodeLoad.getError());
                return refreshMemoryTrackerAndBuildEmptyDecision(
                    "Passing currently perceived capacity as there was a failure gathering node limits [" + nodeLoad.getError() + "]"