Failed to list store metadata for shard request shardId – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve metadata for a specific shard, possibly due to corruption or unavailability of the shard. To resolve this issue, you can try the following: 1) Restart the Elasticsearch node, 2) Check the health status of your cluster and ensure all nodes are functioning properly, 3) If the shard is corrupt, you may need to restore it from a backup, 4) If the error persists, consider reindexing your data. Always ensure your data is backed up to prevent loss.

This guide will help you check for common problems that cause the log ” Failed to list store metadata for shard [” + request.shardId + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, request, indices, metadata.

Log Context

Log “Failed to list store metadata for shard [” + request.shardId + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 protected NodeStoreFilesMetadata nodeOperation(NodeRequest request; Task task) {
 try {
 return new NodeStoreFilesMetadata(clusterService.localNode(); listStoreMetadata(request));
 } catch (IOException e) {
 throw new ElasticsearchException("Failed to list store metadata for shard [" + request.shardId + "]"; e);
 }  private StoreFilesMetadata listStoreMetadata(NodeRequest request) throws IOException {
 final ShardId shardId = request.getShardId();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?