Dropping pending state . more than pending states. – How to solve related issues

Average Read Time

2 Mins

Dropping pending state . more than pending states. – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Dropping pending state . more than pending states. ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, discovery and queue.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “Dropping pending state [{}]. more than [{}] pending states.” classname is PendingClusterStatesQueue.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     /** Add an incoming; not yet committed cluster state */
    public synchronized void addPending(ClusterState state) {
        pendingStates.add(new ClusterStateContext(state));
        if (pendingStates.size() > maxQueueSize) {
            ClusterStateContext context = pendingStates.remove(0);
            logger.warn("dropping pending state [{}]. more than [{}] pending states."; context; maxQueueSize);
            if (context.committed()) {
                context.listener.onNewClusterStateFailed(new ElasticsearchException("too many pending states ([{}] pending)";
                    maxQueueSize));
            }
        }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster