Briefly, this error occurs when Elasticsearch is unable to clean up the snapshot step request for a specific repository. This could be due to a variety of reasons such as insufficient permissions, network issues, or the repository or snapshot not existing. To resolve this issue, you can check if the repository and snapshot exist, ensure the Elasticsearch cluster has the necessary permissions to access the repository, and verify the network connectivity. If the problem persists, consider recreating the repository or snapshot.
This guide will help you check for common problems that cause the log ” cleanup snapshot step request for repository [” + repositoryName + “] and snapshot ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, repository, snapshot, request.
Log Context
Log “cleanup snapshot step request for repository [” + repositoryName + “] and snapshot ” class name is CleanupSnapshotStep.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
@Override
public void onResponse(AcknowledgedResponse acknowledgedResponse) {
if (acknowledgedResponse.isAcknowledged() == false) {
String policyName = indexMetadata.getSettings().get(LifecycleSettings.LIFECYCLE_NAME);
throw new ElasticsearchException("cleanup snapshot step request for repository [" + repositoryName + "] and snapshot " +
"[" + snapshotName + "] policy [" + policyName + "] and index [" + indexName + "] failed to be acknowledged");
}
listener.onResponse(null);
}
