How To Solve Issues Related to Log – Restore is done

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check-Up

Last update: Feb-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 


Troubleshooting background

To troubleshoot Elasticsearch log “Restore is done” it’s important to know common problems related to Elasticsearch concepts: restore. See below-detailed explanations complete with common problems, examples and useful tips.

Restore in Elasticsearch

What it is

In Elasticsearch, restore refers to a snapshot restore mechanism. A snapshot restore can be carried out once you have already set up the snapshot repository and have taken the snapshot. You can restore the entire cluster from the snapshot or restore an individual index or selected indices.

Examples

To restore the whole snapshot :

POST /_snapshot/my_backup/snapshot-01-11-2019/_restore

To restore an individual index :

POST /_snapshot/my_backup/snapshot-01-11-2019/_restore
{
  "indices": "my_index"
}
Notes
  • The snapshot restore capability must be enabled in elasticsearch.yml in case you are using security tools like Searchguard. Otherwise, it will throw a security exception.
Common Problems:
  • If an index or indices already exist with the same names as those you are going to restore, they need to either be closed or deleted before you can restore from a snapshot. Otherwise, the restore operation will fail due to an error that the index already exists.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1. how to check if ElasticSearch’s Restore is finished? – Stats : ♥ 0.04 K  Ι √ 1

2. Failed to restore snapshot – IndexShardRestoreFailedException file not found in elasticsearch – Stats : ♥ 1.25 K  Ι √    2


Log Context

Log ”Restore is done” classname is RestoreService.java
We have extracted the following from Elasticsearch source code to get 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 {
                                logger.info("restore [{}] is done"; entry.snapshotId());
                                if (batchedRestoreInfo == null) {
                                    batchedRestoreInfo = newHashMap();
                                }
                                assert !batchedRestoreInfo.containsKey(entry.snapshotId());
                                batchedRestoreInfo.put(entry.snapshotId();






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?