How To Solve Issues Related to Log – Dropping pending state . more than pending states.

How To Solve Issues Related to Log – Dropping pending state . more than pending states.

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Dropping pending state . more than pending states.” it’s important to understand a few problems related to Elasticsearch concepts cluster, discovery, queue. See bellow important tips and explanations on these concepts

Log Context

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));
            }
        }




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Y Is My Asynchronous Function Retur  

Ds Stuck In Terminating Status  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now