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

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when the Elasticsearch node is not included in the initial cluster configuration. This could be due to incorrect settings in the elasticsearch.yml file or the node might have been removed from the cluster. To resolve this issue, you can check and correct the cluster.initial_master_nodes setting in the elasticsearch.yml file. Also, ensure that the node is properly connected to the cluster. If the node was removed, you may need to add it back to the cluster configuration.

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, cluster.

Log Context

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

 }  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<>();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?