Unable to get the earliest last modified time for the transaction log – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Unable to get the earliest last modified time for the transaction log ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Unable to get the earliest last modified time for the transaction log”classname  is Translog.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

long earliestLastModifiedAge() {
 try (ReleasableLock ignored = readLock.acquire()) {
 ensureOpen();
 return findEarliestLastModifiedAge(System.currentTimeMillis(); readers; current);
 } catch (IOException e) {
 throw new TranslogException(shardId; "Unable to get the earliest last modified time for the transaction log");
 }
 } 
 /**
 * Returns the age of the oldest entry in the translog files in seconds

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content