Bucket bucketName does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.8

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.

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);


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?