Snapshot completed with state – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when the Elasticsearch snapshot process finishes. The state mentioned in the error message indicates the final status of the snapshot. If it’s ‘SUCCESS’, then the snapshot was created without any issues. If it’s ‘FAILED’, then there were problems during the snapshot process. To resolve this, check the Elasticsearch logs for more details about the failure. If it’s a resource issue, consider increasing system resources. If it’s a permission issue, adjust the access rights. If it’s due to a specific index, try excluding that index from the snapshot.

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

Log Context

Log “snapshot [{}] completed with state [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        }; e -> handleFinalizationFailure(e; snapshot; repositoryData));
                        snInfo -> snapshotListeners.addListener(new ActionListener() {
                            public void onResponse(List> actionListeners) {
                                completeListenersIgnoringException(actionListeners; snInfo);
                      "snapshot [{}] completed with state [{}]"; snapshot; snInfo.state());

                            public void onFailure(Exception e) {
                                // never fails


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?