Exception during cleanup of root level blobs – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-7.12

Briefly, this error occurs when Elasticsearch encounters issues while trying to clean up root level blobs, which are typically used for storing snapshots. This could be due to insufficient permissions, disk space issues, or network connectivity problems with the blob storage. To resolve this, you can check and adjust the permissions, ensure there’s enough disk space, and verify the network connectivity. Also, check the health of your blob storage and ensure it’s functioning properly. If the issue persists, consider reconfiguring your snapshot settings or consult with your storage provider.

This guide will help you check for common problems that cause the log ” [{}] Exception during cleanup of root level blobs ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, blobstore.

Log Context

Log “[{}] Exception during cleanup of root level blobs” classname is BlobStoreRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        } catch (Exception e) {
            // TODO: We shouldn't be blanket catching and suppressing all exceptions here and instead handle them safely upstream.
            //       Currently this catch exists as a stop gap solution to tackle unexpected runtime exceptions from implementations
            //       bubbling up and breaking the snapshot functionality.
            assert false : e;
            logger.warn(new ParameterizedMessage("[{}] Exception during cleanup of root level blobs"; metadata.name()); e);
        return Collections.emptyList();

    private DeleteResult cleanupStaleIndices(Map foundIndices; Set survivingIndexIds) {


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?