Running cleanup operations on repository – 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 is performing cleanup operations on a snapshot repository. This could be due to a scheduled maintenance task or a manual trigger. The cleanup operation involves removing unused data from the repository to free up space. If this operation is causing issues, you can resolve it by checking the repository’s health, ensuring there’s enough disk space, and verifying the repository’s configuration. If the cleanup operation is taking too long, consider increasing the timeout settings. Also, ensure that the Elasticsearch cluster has sufficient resources to perform these operations.

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 ” Running cleanup operations on repository [{}][{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, repository, cluster, admin.

Log Context

Log “Running cleanup operations on repository [{}][{}]” classname is TransportCleanupRepositoryAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        final BlobStoreRepository blobStoreRepository = (BlobStoreRepository) repository;
        final ListenableFuture repositoryDataListener = new ListenableFuture();
        repository.getRepositoryData(repositoryDataListener);
        repositoryDataListener.addListener(listener.delegateFailureAndWrap((delegate; repositoryData) -> {
            final long repositoryStateId = repositoryData.getGenId();
            logger.info("Running cleanup operations on repository [{}][{}]"; repositoryName; repositoryStateId);
            submitUnbatchedTask(
                clusterService;
                "cleanup repository [" + repositoryName + "][" + repositoryStateId + ']';
                new ClusterStateUpdateTask() {

 

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