Snapshot is done – How to solve related issues

Snapshot is done – How to solve related issues

Opster Team

Feb-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 is done ” 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: shards and snapshot.

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 [{}] is done” classname is SnapshotShardsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                 // TODO: Add PARTIAL_SUCCESS status?
                                SnapshotsInProgress.Entry updatedEntry = new SnapshotsInProgress.Entry(entry; SnapshotsInProgress.State.SUCCESS; ImmutableMap.copyOf(shards));
                                entries.add(updatedEntry);
                                // Finalize snapshot in the repository
                                snapshotsService.endSnapshot(updatedEntry);
                                logger.info("snapshot [{}] is done"; updatedEntry.snapshotId());
                            }
                        } else {
                            entries.add(entry);
                        }
                    }




 

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

Analyze your cluster