Log Could not find a readable index-N file in a non-empty shard snapshot directory – How To Solve Related Issues


Log Could not find a readable index-N file in a non-empty shard snapshot directory – 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 ” Could not find a readable index-N file in a non-empty shard snapshot directory ” 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: blobstore, discovery-file, repositories, repository-azure 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 “Could not find a readable index-N file in a non-empty shard snapshot directory [{}]” classname is BlobStoreRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 } catch (IOException e) {
                    final String file = SNAPSHOT_INDEX_PREFIX + latest;
                    logger.warn(() -> new ParameterizedMessage("failed to read index file [{}]"; file); e);
                }
            } else if (blobKeys.isEmpty() == false) {
                logger.warn("Could not find a readable index-N file in a non-empty shard snapshot directory [{}]"; blobContainer.path());
            }

            // We couldn't load the index file - falling back to loading individual snapshots
            List snapshots = new ArrayList();
            for (String name : blobKeys) {




 

Optimize Elasticsearch Performance

Try The Tool