Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Failed to update restore state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: restore and snapshots.
Overview
In Elasticsearch, restore refers to the snapshot restore mechanism, which returns indices or clusters to a previous, saved state. 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
- If you are using a security tool like Searchguard, the snapshot restore capability must be enabled in elasticsearch.yml. Otherwise, it will throw a security exception.
Common issues
- 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.
Log Context
Log “Failed to update restore state” classname is RestoreService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
try {
if (event.localNodeMaster()) {
cleanupRestoreState(event);
}
} catch (Exception t) {
logger.warn("Failed to update restore state "; t);
}
}
/**
* Checks if a repository is currently in use by one of the snapshots
Find & fix Elasticsearch problems
