Bucket ” + bucketName + ” does not exist – How to solve this Elasticsearch error

Average Read Time

2 Mins

Bucket ” + bucketName + ” does not exist – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Bucket ” + bucketName + ” does not exist ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories, plugins and repository-gcs.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”Bucket [” + bucketName + “] does not exist”classname  is GoogleCloudStorageBlobStore.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

this.clientName = clientName;
  this.repositoryName = repositoryName;
  this.storageService = storageService;
  this.stats = new GoogleCloudStorageOperationsStats(bucketName);
  if (doesBucketExist(bucketName) == false) {
  throw new BlobStoreException("Bucket [" + bucketName + "] does not exist");
  private Storage client() throws IOException {
  return storageService.client(clientName; repositoryName; stats);


Run the Check-Up to get a customized report like this:

Analyze your cluster