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

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is unable to read metadata from the data store. This could be due to issues like corrupted data, insufficient permissions, or network connectivity problems. To resolve this, you can try restoring from a backup, checking and adjusting the file permissions, or troubleshooting the network connection. Additionally, ensure that the Elasticsearch version is compatible with the data store and that the data store is not full or facing any other issues.

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 and shard.

Log Context

Log “[{}] can’t read metadata from store; responding with empty” classname is TransportNodesListShardStoreMetaData.java.
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 new StoreFilesMetaData(shardId; Store.MetadataSnapshot.EMPTY);
                    } catch (IOException e) {
                        logger.warn(new ParameterizedMessage("[{}] can't read metadata from store; responding with empty"; shardId); e);
                        return new StoreFilesMetaData(shardId; Store.MetadataSnapshot.EMPTY);
                    }
                }
            }
            // try and see if we an list unallocated




 

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?