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

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” local node is not part of initial configuration ” 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: node and cluster.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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();
  knownNodes.add(getLocalNode());
  peerFinder.getFoundPeers().forEach(knownNodes::add);

Run the Check-Up to get a customized report like this:

check-up-dashboard illustration

Try The Tool