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

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot find a local cluster state. This could be due to a node that has lost its data path, a network partition, or a failed master node. To resolve this issue, you can try restarting the node, checking the network connectivity, or promoting another node to be the master. If data loss is suspected, restore from a snapshot. It’s also important to ensure that your cluster has enough nodes to prevent a single point of failure.

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.

Log Context

Log “have no local cluster state” class name 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 {
 final Diff diff;
 final boolean includesLastCommittedData = request.version().onOrAfter(INCLUDES_LAST_COMMITTED_DATA_VERSION);


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?