Snapshot has no segments file – 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 ” Snapshot has no segments file ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, snapshot, blobstore.

Log Context

Log “Snapshot has no segments file”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final Store.MetadataSnapshot sourceMetadata = new Store.MetadataSnapshot(unmodifiableMap(snapshotMetadata); emptyMap(); 0); 
 final StoreFileMetadata restoredSegmentsFile = sourceMetadata.getSegmentsFile();
 if (restoredSegmentsFile == null) {
 throw new IndexShardRestoreFailedException(shardId; "Snapshot has no segments file");
 final Store.RecoveryDiff diff = sourceMetadata.recoveryDiff(recoveryTargetMetadata);
 for (StoreFileMetadata md : diff.identical) {
 BlobStoreIndexShardSnapshot.FileInfo fileInfo = fileInfos.get(;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content