Found stale root level blobs Cleaning them up – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch identifies old or unused root level blobs in the system. These blobs are usually leftover data from previous operations that are no longer needed. The system automatically cleans them up to free up space and maintain optimal performance. To resolve this issue, ensure that your Elasticsearch version is up-to-date as newer versions have improved garbage collection. Also, regularly monitor your system to identify and manually delete any unnecessary data. Lastly, consider optimizing your indexing strategy to prevent the creation of excessive blobs.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

Log “[{}] Found stale root level blobs {}. Cleaning them up” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                final List blobsToLog = -> blobNamesToIgnore.contains(b) == false).toList();
                if (blobsToLog.isEmpty() == false) {
          "[{}] Found stale root level blobs {}. Cleaning them up";; blobsToLog);
            deleteFromContainer(blobContainer(); blobsToDelete.iterator());
            return blobsToDelete;
        } catch (Exception e) {


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?

Get expert answers on Elasticsearch/OpenSearch