Failed to find existing translog files – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” failed to find existing translog files ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “failed to find existing translog files”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// Hold the lock open for the duration of the tool running
 Set translogFiles;
 try {
 translogFiles = filesInDirectory(translogPath);
 } catch (IOException e) {
 throw new ElasticsearchException("failed to find existing translog files"; e);
 final String details = deletingFilesDetails(translogPath; translogFiles); 
 return Tuple.tuple(RemoveCorruptedShardDataCommand.CleanStatus.CORRUPTED; details);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content