Failed to list blobs – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to list or access the blobs (binary large objects) in the repository, often due to incorrect permissions or connectivity issues. To resolve this, you can check the repository’s configuration and ensure that Elasticsearch has the necessary permissions to access it. Also, verify the network connectivity between Elasticsearch and the repository. If the repository is cloud-based, ensure that the cloud service is operational and accessible. Lastly, check if the blob storage is full or not, as this could also cause the error.

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

Log Context

Log “failed to list blobs” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (generation == null) {
 try {
 blobs = shardContainer.listBlobsByPrefix(INDEX_FILE_PREFIX).keySet();
 } catch (IOException e) {
 throw new IndexShardSnapshotFailedException(shardId; "failed to list blobs"; e);
 } else {
 blobs = Collections.singleton(INDEX_FILE_PREFIX + generation);