Could not start datafeed ” + datafeedId +” as indices are being upgraded – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Could not start datafeed ” + datafeedId +” as indices are being upgraded ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices and plugin.


Log Context

Log “Could not start datafeed [” + datafeedId +”] as indices are being upgraded”classname  is DatafeedNodeSelector.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public void checkDatafeedTaskCanBeCreated() {
 if (MlMetadata.getMlMetadata(clusterState).isUpgradeMode()) {
 String msg = "Unable to start datafeed [" + datafeedId +"] explanation [" + AWAITING_UPGRADE.getExplanation() + "]";
 LOGGER.debug(msg);
 Exception detail = new IllegalStateException(msg);
 throw new ElasticsearchStatusException("Could not start datafeed [" + datafeedId +"] as indices are being upgraded";
 RestStatus.TOO_MANY_REQUESTS; detail);
 }
 AssignmentFailure assignmentFailure = checkAssignment();
 if (assignmentFailure != null && assignmentFailure.isCriticalForTaskCreation) {
 String msg = "No node found to start datafeed [" + datafeedId + "]; " +

 

See how you can use AutoOps to resolve issues


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?

Analyze your cluster & get personalized recommendations

Skip to content