Failed to create blob container – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch fails to create a blob container, which is typically used for storing snapshots. This could be due to insufficient permissions, incorrect configuration, or connectivity issues with the storage backend. To resolve this, ensure that Elasticsearch has the necessary permissions to create and access the blob container. Check your configuration settings for any errors and verify that the storage backend (like AWS S3, Azure Storage, etc.) is accessible and functioning properly.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” failed to create blob container ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, plugins, container.

Log Context

Log “failed to create blob container” class name is HdfsBlobStore.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 try {
 mkdirs(path);
 } catch (FileAlreadyExistsException ok) {
 // behaves like Files.createDirectories
 } catch (IOException ex) {
 throw new ElasticsearchException("failed to create blob container"; ex);
 }
 }
 return path;
 }

 

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?