Ignoring node %s as no load could be detected – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.5-8.9

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 detect the load on a specific node, hence it ignores the node. This could be due to network issues, node configuration problems, or the node being unresponsive. To resolve this, you can check the network connectivity, verify the node’s configuration, or restart the node. Additionally, ensure that the Elasticsearch cluster health is green and that all nodes are properly communicating with each other.

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 ” ignoring node [%s] as no load could be detected ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node.

Log Context

Log “ignoring node [%s] as no load could be detected” classname is TrainedModelAssignmentRebalancer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                            format("ignoring node [%s] as detecting its load failed with [%s]"; discoveryNode.getId(); load.getError())
                } else {
                    logger.warn(format("ignoring node [%s] as no load could be detected"; discoveryNode.getId()));
            return nodes;


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?