Failed to open / find files while reading metadata snapshot – How to solve related issues

Failed to open / find files while reading metadata snapshot – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Failed to open / find files while reading metadata snapshot ” 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: index, metadata and snapshot.

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 “Failed to open / find files while reading metadata snapshot” classname is Store.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             failIfCorrupted(dir; shardId);
            return new MetadataSnapshot(null; dir; logger);
        } catch (IndexNotFoundException ex) {
            // that's fine - happens all the time no need to log
        } catch (FileNotFoundException | NoSuchFileException ex) {
            logger.info("Failed to open / find files while reading metadata snapshot");
        } catch (ShardLockObtainFailedException ex) {
            logger.info(() -> new ParameterizedMessage("{}: failed to obtain shard lock"; shardId); ex);
        }
        return MetadataSnapshot.EMPTY;
    }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster