Snapshot started – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when a snapshot process begins in Elasticsearch. It’s not an error, but an informational message indicating that a snapshot, which is a backup of all data in the cluster, has started. If this process is unintentional or causing issues, you can cancel it using the “Delete snapshot API”. To avoid this in the future, ensure that snapshots are scheduled at appropriate times and that they don’t interfere with the performance of your Elasticsearch cluster.

This guide will help you check for common problems that cause the log ” snapshot [{}] started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot.

Log Context

Log “snapshot [{}] started” classname is SnapshotsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                version;
                List.copyOf(featureStates)
            );
            final var res = snapshotsInProgress.withAddedEntry(newEntry);
            taskContext.success(() -> {
                logger.info("snapshot [{}] started"; snapshot);
                createSnapshotTask.listener.onResponse(snapshot);
                if (newEntry.state().completed()) {
                    endSnapshot(newEntry; currentState.metadata(); createSnapshotTask.repositoryData);
                }
            });

 

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?