Current nodes – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch cannot find any nodes currently available in the cluster. This could be due to network issues, configuration errors, or the nodes might be down. To resolve this, you can check the network connectivity between the nodes, verify the cluster settings in the Elasticsearch configuration file, and ensure that all nodes are up and running. If the issue persists, consider checking the Elasticsearch logs for more detailed error information.

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 Elasticsearch concepts: discovery.

Log Context

Log “{}; current nodes: {}” classname is
We extracted the following from Elasticsearch 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?