Briefly, this error occurs when Elasticsearch attempts to start a data frame analytics job from a previously saved state. This could be due to an unexpected shutdown or interruption of the analytics job. To resolve this issue, you can try restarting the Elasticsearch node, ensuring there’s enough disk space, or checking for any network connectivity issues. If the problem persists, consider deleting and recreating the analytics job, ensuring that the job configuration is correct.
This guide will help you check for common problems that cause the log ” [{}] Starting data frame analytics from state [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] Starting data frame analytics from state [{}]” classname is TransportStartDataFrameAnalyticsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
DataFrameAnalyticsTask dfaTask = (DataFrameAnalyticsTask) task;
DataFrameAnalyticsTaskState analyticsTaskState = (DataFrameAnalyticsTaskState) state;
DataFrameAnalyticsState analyticsState = analyticsTaskState == null
? DataFrameAnalyticsState.STOPPED
: analyticsTaskState.getState();
logger.info("[{}] Starting data frame analytics from state [{}]"; params.getId(); analyticsState);
// If we are "stopping" there is nothing to do and we should stop
if (DataFrameAnalyticsState.STOPPING.equals(analyticsState)) {
logger.info("[{}] data frame analytics got reassigned while stopping. Marking as completed"; params.getId());
task.markAsCompleted();
