Blob already exists while – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.4

Briefly, this error occurs when Elasticsearch tries to create a blob that already exists in the system. This usually happens during snapshot creation or restoration. The error indicates a conflict or a synchronization issue. To resolve this, you can try the following: 1) Delete and recreate the snapshot, ensuring no other process is using it. 2) Check for any synchronization issues or network glitches that might cause the system to believe the blob doesn’t exist when it does. 3) Ensure that the blob store isn’t being used by another process or thread at the same time.

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

Log Context

Log “Blob already exists while” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 writeIndexGen(updatedRepositoryData; repositoryStateId);
 } catch (FileAlreadyExistsException ex) {
 // if another master was elected and took over finalizing the snapshot; it is possible
 // that both nodes try to finalize the snapshot and write to the same blobs; so we just
 // log a warning here and carry on
 throw new RepositoryException(; "Blob already exists while " +
 "finalizing snapshot; assume the snapshot has already been saved"; ex);
 } catch (IOException ex) {
 throw new RepositoryException(; "failed to update snapshot in repository"; ex);
 return blobStoreSnapshot;