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

Opster Team

Aug-23, Version: 1-1.3

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 OpenSearch operation.

Briefly, this error occurs when a node tries to join a cluster but is not recognized as part of that cluster. This could be due to incorrect configuration settings, network issues, or mismatched cluster names. To resolve this, ensure that the node and cluster names match in the configuration files. Check the network connectivity between the node and the cluster. Also, verify that the node is properly configured to join the cluster. If the problem persists, consider restarting the node or the entire cluster.

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 OpenSearch concepts: client, cluster, node.

Log Context

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

                    final LivenessResponse livenessResponse = handler.txGet();
                    if (!ignoreClusterName && !clusterName.equals(livenessResponse.getClusterName())) {
                        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?

Get expert answers on Elasticsearch/OpenSearch