Cant read metadata from store; responding with empty – How To Solve Related Issues

Cant read metadata from store; responding with empty – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Cant read metadata from store; responding with empty ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: indices and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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




 

Optimize Elasticsearch Performance

Try The Tool