Failed to get snapshot – How to solve related issues

Average Read Time

2 Mins

Failed to get snapshot – 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 ” Failed to get snapshot ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot, node , cluster and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

                 } else {
                    snapshotSet.add(repository.getSnapshotInfo(snapshotId));
                }
            } catch (Exception ex) {
                if (ignoreUnavailable) {
                    logger.warn(() -> new ParameterizedMessage("failed to get snapshot [{}]"; snapshotId); ex);
                } else {
                    if (ex instanceof SnapshotException) {
                        throw ex;
                    }
                    throw new SnapshotException(repositoryName; snapshotId; "Snapshot could not be read"; ex);




 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content