Failed to check if blob blobName exists – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to verify the existence of a blob in the blob store, which is typically used for snapshot and restore operations. This could be due to network issues, permissions, or the blob store being unavailable. To resolve this, ensure that the blob store is accessible and that Elasticsearch has the necessary permissions to access it. Also, check your network connectivity. If the blob store is a remote server, ensure it’s properly configured and accessible.

This guide will help you check for common problems that cause the log ” Failed to check if blob [” + blobName + “] exists ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository-s3, repositories.

Log Context

Log “Failed to check if blob [” + blobName + “] exists” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public boolean blobExists(String blobName) {
 try (AmazonS3Reference clientReference = blobStore.clientReference()) {
 return SocketAccess.doPrivileged(() -> clientReference.client().doesObjectExist(blobStore.bucket(); buildKey(blobName)));
 } catch (final Exception e) {
 throw new BlobStoreException("Failed to check if blob [" + blobName + "] exists"; e);
 }  @Override
 public InputStream readBlob(String blobName) throws IOException {