Unknown error occurred while updating cluster state – Elasticsearch Error How To Solve Related Issues



Unknown error occurred while updating 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 “Unknown error occurred while updating 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, plugin.


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”Unknown error occurred while updating cluster state”classname  is TransportSetUpgradeModeAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

acknowledgedResponse -> {
  // State change was not acknowledged; we either timed out or ran into some exception
  // We should not continue and alert failure to the end user
  if (acknowledgedResponse.isAcknowledged() == false) {
  logger.info("Cluster state update is NOT acknowledged");
  wrappedListener.onFailure(new ElasticsearchTimeoutException("Unknown error occurred while updating cluster state"));
  return;
  }
 
  // There are no tasks to worry about starting/stopping
  if (tasksCustomMetadata == null || tasksCustomMetadata.tasks().isEmpty()) {

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: Unassigned Shards, how to fix? -views 222,261 ,score 164

Elasticsearch error: cluster_block_exception [FORBIDDEN/12/index read-only / allow delete (api)], flood stage disk watermark exceeded -views   51,428,score 100



Find Configuration Errors

Analyze Now