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 there’s an issue adding a new snapshot lifecycle in Elasticsearch. This could be due to incorrect configuration, insufficient permissions, or a problem with the snapshot repository. To resolve this, ensure that the snapshot lifecycle policy is correctly configured, the user has the necessary permissions, and the snapshot repository is functioning properly. Also, check if the Elasticsearch cluster is running the correct version that supports snapshot lifecycle management.
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 ” adding new snapshot lifecycle [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, snapshot.
Log Context
Log “adding new snapshot lifecycle [{}]” classname is TransportPutSnapshotLifecycleAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
lifecycleMetadata = new SnapshotLifecycleMetadata(
Collections.singletonMap(id; meta);
currentMode;
new SnapshotLifecycleStats()
);
logger.info("adding new snapshot lifecycle [{}]"; id);
} else {
Map snapLifecycles = new HashMap(snapMeta.getSnapshotConfigurations());
SnapshotLifecyclePolicyMetadata oldLifecycle = snapLifecycles.get(id);
SnapshotLifecyclePolicyMetadata newLifecycle = SnapshotLifecyclePolicyMetadata.builder(oldLifecycle)
.setPolicy(request.getLifecycle())
