Snapshot completed with state – How to solve related issues

Snapshot completed with state – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Snapshot completed with state ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: snapshot and snapshots.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

                     entry.shards().size();
                    unmodifiableList(shardFailures);
                    entry.getRepositoryStateId();
                    entry.includeGlobalState());
                removeSnapshotFromClusterState(snapshot; snapshotInfo; null);
                logger.info("snapshot [{}] completed with state [{}]"; snapshot; snapshotInfo.state());
            }

            
Override
            public void onFailure(final Exception e) {
                Snapshot snapshot = entry.snapshot();



 

Run the Check-Up to get a customized report like this:

Analyze your cluster