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

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” prepare target for translog failed ” 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: recovery and indices.

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”prepare target for translog failed”classname  is RecoverySourceHandler.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

stopWatch.stop();
  final TimeValue tookTime = stopWatch.totalTime();
  logger.trace("recovery [phase1]: remote engine start took [{}]"; tookTime);
  listener.onResponse(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");
  cancellableThreads.checkForCancel();
  recoveryTarget.prepareForTranslogOperations(totalTranslogOps; wrappedListener);

 

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

Analyze your cluster