Log Index no longer part of any snapshots in the repository; – How To Solve Related Issues



Log Index no longer part of any snapshots in the repository; – 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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Index no longer part of any snapshots in the repository;” 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, index, repositories, repository-azure, snapshots.


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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”[{}] index [{}] no longer part of any snapshots in the repository;” classname is BlobStoreRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 } catch (DirectoryNotEmptyException dnee) {
                    // if the directory isn't empty for some reason; it will fail to clean up;
                    // we'll ignore that and accept that cleanup didn't fully succeed.
                    // since we are using UUIDs for path names; this won't be an issue for
                    // snapshotting indices of the same name
                    logger.warn(() -> new ParameterizedMessage("[{}] index [{}] no longer part of any snapshots in the repository; " +
                        "but failed to clean up its index folder due to the directory not being empty."; metadata.name(); indexId); dnee);
                } catch (IOException ioe) {
                    // a different IOException occurred while trying to delete - will just log the issue for now
                    logger.warn(() -> new ParameterizedMessage("[{}] index [{}] no longer part of any snapshots in the repository; " +
                        "but failed to clean up its index folder."; metadata.name(); indexId); ioe);




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 28322  

Github Issue Number 48897  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now