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

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

Opster Team

July-20, 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 that cause 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (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");
  incompatibleClusterStateDiffReceivedCount.incrementAndGet();
  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

 

Optimize Elasticsearch Performance

Try The Tool