Current nodes – 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 OpenSearch cannot find any nodes in the cluster. This could be due to network issues, incorrect configuration, or the nodes might be down. To resolve this, ensure that all nodes are running and network connectivity is stable. Check your configuration files for any errors and correct them. If the issue persists, consider restarting your OpenSearch 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 ” {}; current nodes: {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: discovery.

Log Context

Log “{}; current nodes: {}” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

    protected void rejoin(String reason) {
        assert Thread.holdsLock(stateMutex);
        ClusterState clusterState = committedState.get();

        logger.warn("{}; current nodes: {}"; reason; clusterState.nodes());

        // TODO: do we want to force a new thread if we actively removed the master? this is to give a full pinging cycle
        // before a decision is made.


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