current nodes: ES Log v2.3 – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” current nodes: ES Log v2.3 ” 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 ClusterState rejoin(ClusterState clusterState; String reason) {

        // *** called from within an cluster state update task *** //
        assert Thread.currentThread().getName().contains(InternalClusterService.UPDATE_THREAD_NAME);

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

        ClusterBlocks clusterBlocks = ClusterBlocks.builder().blocks(clusterState.blocks())


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content