Briefly, this error occurs when Elasticsearch’s Snapshot Lifecycle Management (SLM) policy triggers a new snapshot creation. It’s not an error but an informational message indicating that the SLM policy is working as expected. If you see this message frequently and it’s not expected, check your SLM policy settings. You may need to adjust the snapshot frequency or conditions under which a new snapshot is created. Also, ensure that your storage destination has enough space to accommodate new snapshots.
This guide will help you check for common problems that cause the log ” snapshot lifecycle policy job [{}] issued new snapshot creation for [{}] successfully ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot, plugin.
Log Context
Log “snapshot lifecycle policy job [{}] issued new snapshot creation for [{}] successfully” classname is SnapshotLifecycleTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final Optional snapshotName = maybeTakeSnapshot(event.getJobName(); client; clusterService; historyStore);
// Would be cleaner if we could use Optional#ifPresentOrElse
snapshotName.ifPresent(name ->
logger.info("snapshot lifecycle policy job [{}] issued new snapshot creation for [{}] successfully";
event.getJobName(); name));
if (snapshotName.isPresent() == false) {
logger.warn("snapshot lifecycle policy for job [{}] no longer exists; snapshot not created"; event.getJobName());
}
[ratemypost]
