Failed to parse repository ; uuid not a string – How to solve this Elasticsearch error

Average Read Time

2 Mins

Failed to parse repository ; uuid not a string – How to solve this Elasticsearch error

Opster Team

March-22, 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 ” failed to parse repository ; uuid not a string ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, metadata, repository.

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 “failed to parse repository [{}]; uuid not a string”classname  is RepositoriesMetadata.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 if (token == XContentParser.Token.FIELD_NAME) {
 String currentFieldName = parser.currentName();
 if ("uuid".equals(currentFieldName)) {
 if (parser.nextToken() != XContentParser.Token.VALUE_STRING) {
 throw new ElasticsearchParseException("failed to parse repository [{}]; uuid not a string"; name);
 }
 uuid = parser.text();
 } else if ("type".equals(currentFieldName)) {
 if (parser.nextToken() != XContentParser.Token.VALUE_STRING) {
 throw new ElasticsearchParseException("failed to parse repository [{}]; unknown type"; name);

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content