Failed to associate a new translog – How to solve this Elasticsearch error

Failed to associate a new translog – 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 ” failed to associate a new translog ” 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: plugin.

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”failed to associate a new translog”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final long primaryTerm = indexShard.getPendingPrimaryTerm();
  final String translogUUID = segmentInfos.userData.get(Translog.TRANSLOG_UUID_KEY);
  final Path translogLocation = indexShard.shardPath().resolveTranslog();
  Translog.createEmptyTranslog(translogLocation; shardId; localCheckpoint; primaryTerm; translogUUID; null);
  } catch (Exception e) {
  throw new TranslogException(shardId; "failed to associate a new translog"; e);


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

Analyze your cluster