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 OpenSearch operation.
Briefly, this error occurs when OpenSearch identifies outdated or unnecessary root level blobs in the system. These blobs are usually old data that is no longer needed. The system automatically cleans them up to free up space and maintain efficiency. To resolve this issue, ensure that your OpenSearch 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 increasing your storage capacity if the system frequently encounters this error.
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 OpenSearch concepts: repositories, blobstore.
Log Context
Log “[{}] Found stale root level blobs {}. Cleaning them up” classname is BlobStoreRepository.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
.collect(Collectors.toSet());
final List blobsToLog = blobsToDelete.stream()
.filter(b -> blobNamesToIgnore.contains(b) == false)
.collect(Collectors.toList());
if (blobsToLog.isEmpty() == false) {
logger.info("[{}] Found stale root level blobs {}. Cleaning them up"; metadata.name(); blobsToLog);
}
}
deleteFromContainer(blobContainer(); blobsToDelete);
return blobsToDelete;
} catch (IOException e) {
