Node not part of the cluster ignoring – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.17

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 a node in Elasticsearch is not recognized as part of the cluster. This could be due to incorrect configuration settings, network issues, or mismatched cluster names. To resolve this, ensure that all nodes have the same cluster name in the elasticsearch.yml file. Also, check the network settings and ensure that all nodes are reachable. If the problem persists, try restarting the Elasticsearch service on the affected node.

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 ” node {} not part of the cluster {}; ignoring… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: client, cluster, node.

Log Context

Log “node {} not part of the cluster {}; ignoring…” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        TransportRequestOptions.of(pingTimeout; TransportRequestOptions.Type.STATE);
                    final LivenessResponse livenessResponse = handler.txGet();
                    if (ignoreClusterName == false && clusterName.equals(livenessResponse.getClusterName()) == false) {
                        logger.warn("node {} not part of the cluster {}; ignoring..."; listedNode; clusterName);
                    } else {
                        // use discovered information but do keep the original transport address;
                        // so people can control which address is exactly used.
                        DiscoveryNode nodeWithInfo = livenessResponse.getDiscoveryNode();


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?