Found nodeMetadata which is compatible with current version – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-7.15

Briefly, this error occurs when Elasticsearch detects a node with a version that is compatible with the current version of the cluster. This could be due to a node rejoining the cluster after an upgrade or a failed downgrade. To resolve this issue, ensure all nodes in the cluster are running the same version of Elasticsearch. If you’re upgrading, follow the correct rolling upgrade process. If a node was unintentionally downgraded, upgrade it to match the cluster version. Always backup your data before making version changes.

This guide will help you check for common problems that cause the log ” found [” + nodeMetadata + “] which is compatible with current version [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, node, version.

Log Context

Log “found [” + nodeMetadata + “] which is compatible with current version [” class name is OverrideNodeVersionCommand.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ElasticsearchException(NO_METADATA_MESSAGE);
 }  try {
 nodeMetadata.upgradeToCurrentVersion();
 throw new ElasticsearchException("found [" + nodeMetadata + "] which is compatible with current version [" + Version.CURRENT
 + "]; so there is no need to override the version checks");
 } catch (IllegalStateException e) {
 // ok; means the version change is not supported
 }

 

 [ratemypost]