Log current nodes: ES Log v2.3 – How To Solve Related Issues

Log 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 try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “current nodes: ES Log v2.3” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: discovery.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”; current nodes: {}” classname is ZenDiscovery.java
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())


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Curl For Current Node Write Consist  

Node Disconnects Every Hour  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now