Failed to clean up old shard generation blobs – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-8.9

Briefly, this error occurs when Elasticsearch is unable to delete old shard generation blobs due to issues like insufficient permissions, disk space, or network connectivity. To resolve this, you can check and adjust the permissions of the Elasticsearch directory, ensure there’s enough disk space, and verify network connectivity. Also, consider checking the health of your Elasticsearch cluster and ensure it’s not in a red state. If the issue persists, you might need to manually delete the old shard generation blobs.

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

Log Context

Log “Failed to clean up old shard generation blobs” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (toDelete.isEmpty() == false) {
            threadPool.executor(ThreadPool.Names.SNAPSHOT).execute(() -> {
                try {
                    deleteFromContainer(blobContainer(); toDelete.iterator());
                } catch (Exception e) {
                    logger.warn("Failed to clean up old shard generation blobs"; e);
                } finally {
        } else {


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?