Delete repository – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.11

Briefly, this error occurs when you try to delete a repository in Elasticsearch that doesn’t exist or is currently in use. It could also be due to insufficient permissions. To resolve this issue, ensure that the repository you’re trying to delete exists and is not in use. If it’s in use, wait until the operation using it completes. Also, check your user permissions to ensure you have the rights to delete repositories. If the repository is corrupted, you may need to manually delete it from the file system.

This guide will help you check for common problems that cause the log ” delete repository [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository, repositories, delete.

 
 

repository

 
 

repositories

Overview

An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported: 

Repository types

Repository typeConfiguration type
Shared file systemType: “fs”
S3Type : “s3”
HDFSType :“hdfs”
AzureType: “azure”
Google Cloud StorageType : “gcs”

Examples

To register an “fs” repository:

PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
  }
}

Notes and good things to know

  • S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
  • The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
  • When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
 
 

delete

Overview

DELETE is an Elasticsearch API which removes a document from a specific index. This API requires an index name and _id document to delete the document. 

Delete a document

DELETE /my_index/_doc/1

Notes

  • A delete request throws 404 error code if the document does not already exist in the index.
  • If you want to delete a set of documents that  matches a query, you need to use delete by query API.

Log Context

Log “delete repository [{}]” classname is RepositoriesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        List repositoriesMetadata = new ArrayList(repositories.repositories().size());
                        boolean changed = false;
                        for (RepositoryMetadata repositoryMetadata : repositories.repositories()) {
                            if (Regex.simpleMatch(request.name(); repositoryMetadata.name())) {
                                ensureRepositoryNotInUse(currentState; repositoryMetadata.name());
                                logger.info("delete repository [{}]"; repositoryMetadata.name());
                                changed = true;
                            } else {
                                repositoriesMetadata.add(repositoryMetadata);
                            }
                        }

 

 [ratemypost]

Related Articles

Back to all articles