Cannot start data frame analytics – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.5-7.1

Briefly, this error occurs when Elasticsearch is unable to initiate the data frame analytics due to issues like insufficient memory, incorrect configuration, or lack of necessary permissions. To resolve this, you can increase the memory allocation, check and correct the configuration settings, or ensure the user has the required permissions to start data frame analytics. Additionally, ensure that the data frame analytics feature is enabled in your Elasticsearch version as it’s not available in all versions.

This guide will help you check for common problems that cause the log ” Cannot start data frame analytics [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Cannot start data frame analytics [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  @Override
 public void onFailure(Exception e) {
 if (ExceptionsHelper.unwrapCause(e) instanceof ResourceAlreadyExistsException) {
 e = new ElasticsearchStatusException("Cannot start data frame analytics [" + request.getId() +
 "] because it has already been started"; RestStatus.CONFLICT; e);


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?