Version string expected min_version – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 Error 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. 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: repositories and version.

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”version string expected [min_version]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException("start object expected [" + INDEX_METADATA_IDENTIFIERS + "]");
  } 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 + "]");


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

Analyze your cluster