Restore 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 ” Restore is done ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: restore.

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

                        if (shards != null) {
                            if (!completed(shards)) {
                                entries.add(new RestoreInProgress.Entry(entry.snapshotId(); RestoreInProgress.State.STARTED; entry.indices(); ImmutableMap.copyOf(shards)));
                            } else {
                      "restore [{}] is done"; entry.snapshotId());
                                if (batchedRestoreInfo == null) {
                                    batchedRestoreInfo = newHashMap();
                                assert !batchedRestoreInfo.containsKey(entry.snapshotId());


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content