Prepare target for translog failed – How to solve this Elasticsearch error

Opster Team

July-20, 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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” prepare target for translog failed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery and indices.


Log Context

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

 final TimeValue tookTime = stopWatch.totalTime();
 logger.trace("recovery [phase1]: remote engine start took [{}]"; tookTime);
 e -> listener.onFailure(new RecoveryEngineException(shard.shardId(); 1; "prepare target for translog failed"; e)));
 // Send a request preparing the new shard's translog to receive operations. This ensures the shard engine is started and disables
 // garbage collection (not the JVM's GC!) of tombstone deletes.
 logger.trace("recovery [phase1]: prepare remote engine for translog");
 recoveryTarget.prepareForTranslogOperations(totalTranslogOps; wrappedListener);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content