Could not start data frame analytics task allocation explanation – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-7.1

Briefly, this error occurs when Elasticsearch is unable to allocate resources to start a data frame analytics task. This could be due to insufficient memory, disk space, or other system resources. To resolve this issue, you can try increasing the system resources, optimizing your data frame analytics task to use less resources, or distributing your tasks across multiple nodes if you’re running in a cluster environment. Additionally, check your Elasticsearch configuration settings to ensure they are not limiting resource allocation.

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: plugin, allocation.

Log Context

Log “Could not start data frame analytics task; allocation explanation [” class name is 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();


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?