Failed to list directory some of files might not be deleted – 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 list directory some of files might not be deleted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, discovery-file, repositories and restore.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “[{}] [{}] failed to list directory – some of files might not be deleted” classname is FileRestoreContext.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     } catch (IOException e) {
                        logger.warn("[{}] [{}] failed to delete file [{}] during snapshot cleanup"; shardId; snapshotId; storeFile);
                    }
                }
            } catch (IOException e) {
                logger.warn("[{}] [{}] failed to list directory - some of files might not be deleted"; shardId; snapshotId);
            }
        } finally {
            store.decRef();
        }
    }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content