Could not start data frame analytics task; allocation explanation – 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 data frame analytics task; allocation explanation ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: allocation 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 data frame analytics task; allocation explanation [“classname  is TransportStartDataFrameAnalyticsAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// Assignment failed due to primary shard check.
 // This is hopefully intermittent and we should allow another assignment attempt.
 if (assignmentExplanation.contains(PRIMARY_SHARDS_INACTIVE)) {
 return false;
 }
 exception = new ElasticsearchStatusException("Could not start data frame analytics task; allocation explanation [" +
 assignment.getExplanation() + "]"; RestStatus.TOO_MANY_REQUESTS);
 return true;
 }
 DataFrameAnalyticsTaskState taskState = (DataFrameAnalyticsTaskState) persistentTask.getState();
 DataFrameAnalyticsState analyticsState = taskState == null ? DataFrameAnalyticsState.STOPPED : taskState.getState();

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content