Node is selected as the current health node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch selects a node as the current health node, which is responsible for monitoring the health of the cluster. This is not necessarily an error, but more of an informational message. However, if you’re seeing issues, it could be due to network partitions, high load, or configuration issues. To resolve this, ensure all nodes are properly configured and network connectivity is stable. Also, monitor your cluster’s load to prevent any node from being overwhelmed. If necessary, consider adding more nodes to your cluster to distribute the load.

This guide will help you check for common problems that cause the log ” Node [{{}}{{}}] is selected as the current health node. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Log Context

Log “Node [{{}}{{}}] is selected as the current health node.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    protected void nodeOperation(AllocatedPersistentTask task; HealthNodeTaskParams params; PersistentTaskState state) {
        HealthNode healthNode = (HealthNode) task;
        DiscoveryNode node = clusterService.localNode();"Node [{{}}{{}}] is selected as the current health node."; node.getName(); node.getId());

    protected HealthNode createTask(
        long id;


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?