Briefly, this error occurs when Elasticsearch’s data frame analytics job is being stopped but gets reassigned to another node during the process. This could be due to node failures or cluster rebalancing. To resolve this issue, ensure that the cluster is stable and not under heavy load. Also, check the health of your nodes and replace any that are consistently failing. Additionally, consider adjusting the cluster settings to limit the frequency of rebalancing.
This guide will help you check for common problems that cause the log ” [{}] data frame analytics got reassigned while stopping. Marking as completed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] data frame analytics got reassigned while stopping. Marking as completed” classname is TransportStartDataFrameAnalyticsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
: 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();
return;
}
// If we are "failed" then we should leave the task as is; for recovery it must be force stopped.
if (DataFrameAnalyticsState.FAILED.equals(analyticsState)) {
[ratemypost]
