Timed out waiting for all nodes to process published state timeout pending nodes – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

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 Elasticsearch nodes take too long to respond to a cluster state update, causing a timeout. This could be due to network issues, overloaded nodes, or slow hardware. To resolve this, you can increase the ‘discovery.zen.publish_timeout’ setting to allow more time for nodes to respond. Alternatively, you can investigate the cause of the delay, such as checking for network issues or high resource usage on the nodes. If the issue is due to slow hardware, consider upgrading your hardware or optimizing your Elasticsearch configuration to reduce resource usage.

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 ” timed out waiting for all nodes to process published state [{}] (timeout [{}]; pending nodes: {}) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery.

Log Context

Log “timed out waiting for all nodes to process published state [{}] (timeout [{}]; pending nodes: {})” classname is PublishClusterStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    publishResponseHandler.awaitAllNodes(TimeValue.timeValueNanos(timeLeftInNanos)) == false);
            if (sendingController.getPublishingTimedOut()) {
                DiscoveryNode[] pendingNodes = publishResponseHandler.pendingNodes();
                // everyone may have just responded
                if (pendingNodes.length > 0) {
                    logger.warn("timed out waiting for all nodes to process published state [{}] (timeout [{}]; pending nodes: {})";
                        clusterState.version(); publishTimeout; pendingNodes);
            // The failure is logged under debug when a sending failed. we now log a summary.
            Set failedNodes = publishResponseHandler.getFailedNodes();


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?