Empty restore source – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you attempt to restore an Elasticsearch snapshot, but the source of the snapshot is empty or not correctly specified. This could be due to a misconfiguration or a missing snapshot. To resolve this issue, you can verify the snapshot source and ensure it’s correctly specified. Also, check if the snapshot exists in the repository. If it doesn’t, you need to create a new snapshot. Lastly, ensure that the Elasticsearch cluster has the necessary permissions to access the snapshot repository.

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: restore, shard, index, source.

Log Context

Log “empty restore source” class name 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());
 indexShard.preRecovery(outerListener.delegateFailure((listener; ignored) -> {  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);