Have no local cluster state – Elasticsearch Error How To Solve Related Issues

Have no local cluster state – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

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


This guide will help you check for common problems that cause the log “have no local cluster state” 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.

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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

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 Elasticsearch not starting, but throwing ReceiveTimeoutTransportException -views 1,972 

Failed to get local cluster state Critical issue – Elasticsearch …  

Find Configuration Errors

Analyze Now