Cant read metadata from store. will not reuse any local file while restoring – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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 ” Cant read metadata from store. will not reuse any local file while restoring ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repositories and repository-azure.

Log Context

Log “{} Can’t read metadata from store; will not reuse any local file while restoring” classname is BlobStoreRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 } catch (IndexNotFoundException e) {
                    // happens when restore to an empty shard; not a big deal
                    logger.trace("[{}] [{}] restoring from to an empty shard"; shardId; snapshotId);
                    recoveryTargetMetadata = Store.MetadataSnapshot.EMPTY;
                } catch (IOException e) {
                    logger.warn((Supplier>) () -> new ParameterizedMessage("{} Can't read metadata from store; will not reuse any local file while restoring"; shardId); e);
                    recoveryTargetMetadata = Store.MetadataSnapshot.EMPTY;
                }

                final List filesToRecover = new ArrayList();
                final Map snapshotMetaData = new HashMap();




 

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?

Analyze your cluster & get personalized recommendations

Skip to content