Briefly, this error occurs when you’re trying to access a bucket in Elasticsearch that doesn’t exist. This could be due to a typo in the bucket name or the bucket was deleted. To resolve this issue, you can verify the bucket name for any typos or check if the bucket was accidentally deleted. If the bucket was deleted, you will need to recreate it. If the bucket name is correct and it still doesn’t exist, you may need to create it before trying to access it.
This guide will help you check for common problems that cause the log ” Bucket [” + bucketName + “] does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, plugins, repository-gcs.
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 “Bucket [” + bucketName + “] does not exist” class name is GoogleCloudStorageBlobStore.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
GoogleCloudStorageBlobStore(String bucketName; String clientName; GoogleCloudStorageService storageService) {
this.bucketName = bucketName;
this.clientName = clientName;
this.storageService = storageService;
if (doesBucketExist(bucketName) == false) {
throw new BlobStoreException("Bucket [" + bucketName + "] does not exist");
}
} private Storage client() throws IOException {
return storageService.client(clientName);
