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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 + "]; " +

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content