current nodes: – How to solve related issues

Average Read Time

2 Mins

current nodes: – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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.


Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content