Cluster state with version that is published locally has neither been processed nor failed – How to solve related issues

Cluster state with version that is published locally has neither been processed nor failed – 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 ” Cluster state with version that is published locally has neither been processed nor failed ” 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 version.

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

Log “Cluster state with version [{}] that is published locally has neither been processed nor failed” classname is ZenDiscovery.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
            boolean sentToApplier = processNextCommittedClusterState("master " + newState.nodes().getMasterNode() +
                " committed version [" + newState.version() + "] source [" + clusterChangedEvent.source() + "]");
            if (sentToApplier == false && processedOrFailed.get() == false) {
                assert false : "cluster state published locally neither processed nor failed: " + newState;
                logger.warn("cluster state with version [{}] that is published locally has neither been processed nor failed";
                    newState.version());
                return;
            }
        }
        // indefinitely wait for cluster state to be applied locally




 

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

Analyze your cluster