Could not start data frame analytics task; allocation explanation – Elasticsearch Error How To Solve Related Issues


Could not start data frame analytics task; allocation explanation – 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 ” Could not start data frame analytics task; allocation explanation ” 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: allocation and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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();

 

Optimize Elasticsearch Performance

Try The Tool