Restore is done – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when the restore process of an Elasticsearch snapshot is completed. It’s not an error, but a status message indicating that the restore operation has been successfully finished. If you’re seeing this message unexpectedly, it might be due to an automated script or process that’s triggering the restore. To resolve this, you can check your automated tasks or scripts related to Elasticsearch. Also, ensure that the restored data is accurate and complete. If not, you may need to re-run the restore operation or check the snapshot’s integrity.

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.

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());


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?