Failed to flush shard on translog threshold – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to flush a shard due to reaching the translog threshold. This could be due to insufficient disk space, high indexing rate, or a slow disk. To resolve this issue, you can increase the translog threshold, ensure there is enough disk space, or optimize your indexing operations. Additionally, consider upgrading your hardware for better performance, particularly the disk speed.

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

Log Context

Log “failed to flush shard on translog threshold” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     logger.trace("ignoring EsRejectedExecutionException; shutting down"; t);

                public void onFailure(Throwable t) {
                    logger.warn("failed to flush shard on translog threshold"; t);

                protected void doRun() throws Exception {


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?