Uuid repositoryUuid original name originalName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.12-8.9

Briefly, this error occurs when there is a mismatch between the UUID of the Elasticsearch repository and the original name. This could be due to a misconfiguration or a change in the repository settings. To resolve this issue, you can try the following: 1) Verify the repository settings and ensure the UUID matches the original name. 2) If the settings are correct, try to recreate the repository with the correct UUID and original name. 3) If the error persists, consider restoring from a backup or reindexing your data.

This guide will help you check for common problems that cause the log ” uuid [” + repositoryUuid + “]; original name [” + originalName + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository, plugin.

Log Context

Log “uuid [” + repositoryUuid + “]; original name [” + originalName + “]” class name is SearchableSnapshotDirectory.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 for (Repository repository : repositories.values()) {
 if (repository.getMetadata().uuid().equals(repositoryUuid)) {
 return repository;
 throw new RepositoryMissingException("uuid [" + repositoryUuid + "]; original name [" + originalName + "]");
 }  /**
 * A {@link FilterBlobContainer} that uses {@link BlobStoreRepository#maybeRateLimitRestores(InputStream)} to limit the rate at which
 * blobs are read from the repository.


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?