Stop throttling indexing for shard – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch resumes normal indexing after it had previously slowed down or throttled the indexing process due to high memory pressure. This is not an error but an informational message indicating that the system is returning to normal operation. To avoid throttling in the future, consider increasing the JVM heap size, optimizing your indexing process, or upgrading your hardware to better handle the load. Also, regularly monitor your cluster’s health and performance to identify potential issues early.

This guide will help you check for common problems that cause the log ” stop throttling indexing for shard [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, indexing, shard.

Log Context

Log “stop throttling indexing for shard [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            if (doThrottle == false) {
                for (IndexShard shard : throttled) {
          "stop throttling indexing for shard [{}]"; shard.shardId());


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?