Failed to roll translog – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to roll the transaction log (translog). This could be due to insufficient disk space, file system issues, or a corrupted translog. To resolve this, you can try freeing up disk space, checking the file system for errors, or recovering the corrupted translog. If the issue persists, consider reindexing your data. Always ensure to have a backup of your data to prevent data loss.

This guide will help you check for common problems that cause the log ” failed to roll translog ” 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 roll translog” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 try {
 failEngine("translog trimming failed"; e);
 } catch (Exception inner) {
 throw new EngineException(shardId; "failed to roll translog"; e);
 }  @Override
 public void trimUnreferencedTranslogFiles() throws EngineException {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?