Briefly, this error occurs when there’s an issue with the Snapshot Lifecycle Management (SLM) policy in Elasticsearch. SLM policies allow automatic creation, deletion and retention of snapshots. The error indicates a problem with manually triggering the snapshot retention. To resolve this, ensure that the SLM policy is correctly configured and that the Elasticsearch cluster has the necessary permissions to execute the policy. Also, check if the snapshot repository is accessible and the disk has enough space. Lastly, ensure that the Elasticsearch version supports the SLM feature.
This guide will help you check for common problems that cause the log ” manually triggering SLM snapshot retention ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, snapshot.
Log Context
Log “manually triggering SLM snapshot retention” classname is TransportExecuteSnapshotRetentionAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final ExecuteSnapshotRetentionAction.Request request;
final ClusterState state;
final ActionListener listener
) {
try {
logger.info("manually triggering SLM snapshot retention");
this.retentionService.triggerRetention();
listener.onResponse(AcknowledgedResponse.TRUE);
} catch (Exception e) {
listener.onFailure(new ElasticsearchException("failed to execute snapshot lifecycle retention"; e));
}
[ratemypost]