Failed to turn off translog retention – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-7.17

Briefly, this error occurs when Elasticsearch is unable to disable the translog retention, which is a mechanism that keeps operations in the transaction log for a certain period of time. This could be due to insufficient permissions, disk space issues, or a configuration error. To resolve this issue, you can check and adjust the user permissions, ensure there is enough disk space, or review and correct the Elasticsearch configuration settings. Additionally, you may need to restart the Elasticsearch service after making these changes.

This guide will help you check for common problems that cause the log ” failed to turn off translog retention ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, shard.

Log Context

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

        // Off to the generic threadPool as pruning the delete tombstones can be expensive.
        threadPool.generic().execute(new AbstractRunnable() {
            public void onFailure(Exception e) {
                if (state != IndexShardState.CLOSED) {
                    logger.warn("failed to turn off translog retention"; e);

            protected void doRun() {


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?