Empty restore source – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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.

This guide will help you check for common problems that cause the log ” empty restore source ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index, restore, source.

Log Context

Log “empty restore source”classname  is StoreRecovery.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

) {
 logger.debug("restoring from {} ..."; indexShard.recoveryState().getRecoverySource());
 final RecoveryState.Translog translogState = indexShard.recoveryState().getTranslog();
 if (restoreSource == null) {
 listener.onFailure(new IndexShardRestoreFailedException(shardId; "empty restore source"));
 if (logger.isTraceEnabled()) {
 logger.trace("[{}] restoring shard [{}]"; restoreSource.snapshot(); shardId);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content