Version string expected min_version – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” version string expected min_version ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories and version.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “version string expected [min_version]”classname  is RepositoryData.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException("start object expected [" + INDEX_METADATA_IDENTIFIERS + "]");
 }
 indexMetaIdentifiers.putAll(parser.mapStrings());
 } else if (MIN_VERSION.equals(field)) {
 if (parser.nextToken() != XContentParser.Token.VALUE_STRING) {
 throw new ElasticsearchParseException("version string expected [min_version]");
 }
 final Version version = Version.fromString(parser.text());
 assert SnapshotsService.useShardGenerations(version);
 } else {
 throw new ElasticsearchParseException("unknown field name [" + field + "]");

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content