Error while listing local files; recovering as if there are none – How to solve related issues

Error while listing local files; recovering as if there are none – 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 ” Error while listing local files; recovering as if there are none ” 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: indices and recovery.

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 “Error while listing local files; recovering as if there are none” classname is PeerRecoveryTargetService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         } catch (final org.apache.lucene.index.IndexNotFoundException e) {
            // happens on an empty folder. no need to log
            logger.trace("{} shard folder empty; recovering all files"; recoveryTarget);
            return Store.MetadataSnapshot.EMPTY;
        } catch (final IOException e) {
            logger.warn("error while listing local files; recovering as if there are none"; e);
            return Store.MetadataSnapshot.EMPTY;
        }
    }

    /**




 

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

Analyze your cluster