Local node is not part of initial configuration – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” local node is not part of initial configuration ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and cluster.

Log Context

Log “local node is not part of initial configuration”classname  is Coordinator.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

"this node is not master-eligible; but cluster bootstrapping can only happen on a master-eligible node");
 if (votingConfiguration.getNodeIds().contains(getLocalNode().getId()) == false) {
 logger.debug("skip setting initial configuration as local node is not part of initial configuration");
 throw new CoordinationStateRejectedException("local node is not part of initial configuration");
 final List knownNodes = new ArrayList<>();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content