Have no local cluster state – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” have no local cluster state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “have no local cluster state”classname  is PublicationTransportHandler.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else {
 final ClusterState lastSeen = lastSeenClusterState.get();
 if (lastSeen == null) {
 logger.debug("received diff for but don't have any local cluster state - requesting full state");
 throw new IncompatibleClusterStateVersionException("have no local cluster state");
 } else {
 ClusterState incomingState;
 try {
 Diff diff = ClusterState.readDiffFrom(in; lastSeen.nodes().getLocalNode());
 incomingState = diff.apply(lastSeen); // might throw IncompatibleClusterStateVersionException


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content