Too many pending states pending – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

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 Elasticsearch operation.

Briefly, this error occurs when there are too many cluster state updates that are yet to be processed by Elasticsearch. This could be due to a high rate of index creation, deletion, or updates to cluster settings. To resolve this issue, you can consider reducing the rate of these operations or increasing the capacity of your Elasticsearch cluster. Additionally, ensure that your cluster’s master node is not overwhelmed with other tasks, as this could slow down the processing of cluster state updates.

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 ” too many pending states ([{}] pending) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery.

Log Context

Log “too many pending states ([{}] pending)” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (pendingStates.size() > maxQueueSize) {
 ClusterStateContext context = pendingStates.remove(0);
 logger.warn("dropping pending state [{}]. more than [{}] pending states."; context; maxQueueSize);
 if (context.committed()) {
 new ElasticsearchException("too many pending states ([{}] pending)"; maxQueueSize)


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?