Briefly, this error occurs when there is an issue with creating or updating a repository in Elasticsearch. This could be due to incorrect repository settings, insufficient permissions, or connectivity issues with the repository. To resolve this, ensure that the repository settings are correct and that Elasticsearch has the necessary permissions to access the repository. If the repository is remote, check the network connectivity. Also, ensure that the repository plugin (if any) is properly installed and compatible with your Elasticsearch version.
This guide will help you check for common problems that cause the log ” put repository [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, repository.
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 type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “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.
Log Context
Log “put repository [{}]” classname is RepositoriesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
public void clusterStateProcessed(ClusterState oldState; ClusterState newState) {
if (changed) {
if (found) {
logger.info("updated repository [{}]"; request.name());
} else {
logger.info("put repository [{}]"; request.name());
}
}
publicationStep.onResponse(oldState != newState);
}
});
