Can t read metadata from store responding with empty – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.2

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to read metadata from the store, possibly due to corruption or unavailability of the data store. To resolve this issue, you can try the following: 1) Check the health status of your Elasticsearch cluster and ensure all nodes are functioning properly. 2) Verify the integrity of your data store and fix any corruption issues. 3) If the data store is unavailable, ensure it is properly connected and accessible. 4) If the error persists, consider restoring from a backup.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [{}] can’t read metadata from store; responding with empty ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, metadata.

Log Context

Log “[{}] can’t read metadata from store; responding with empty” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        return storeFilesMetadata;
                    } catch (org.apache.lucene.index.IndexNotFoundException e) {
                        logger.trace(new ParameterizedMessage("[{}] node is missing index; responding with empty"; shardId); e);
                        return StoreFilesMetadata.EMPTY;
                    } catch (IOException e) {
                        logger.warn(new ParameterizedMessage("[{}] can't read metadata from store; responding with empty"; shardId); e);
                        return StoreFilesMetadata.EMPTY;
            final String customDataPath;


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?