Now throttling indexing for shard segment writing can t keep up – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch is unable to index data at the rate it’s being received, causing a backlog in the indexing process. This could be due to insufficient resources, such as CPU, memory, or disk I/O. To resolve this issue, you could consider scaling up your resources, optimizing your indexing process by reducing the size or complexity of the documents being indexed, or increasing the refresh interval. Additionally, you could also consider using bulk requests for indexing, or partitioning your data across more shards to distribute the load.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” now throttling indexing for shard [{}]: segment writing can’t keep up ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: indices, indexing, shard.

Log Context

Log “now throttling indexing for shard [{}]: segment writing can’t keep up” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                        new ByteSizeValue(largest.bytesUsed)
                    totalBytesUsed -= largest.bytesUsed;
                    if (doThrottle && throttled.contains(largest.shard) == false) {
              "now throttling indexing for shard [{}]: segment writing can't keep up"; largest.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?

Get expert answers on Elasticsearch/OpenSearch