Briefly, this error occurs when an abort request is sent to a running data frame transform in Elasticsearch. This could be due to a manual stop request or an automatic abort due to system constraints. To resolve this issue, you can restart the data frame transform if it was stopped manually. If it was an automatic abort, you may need to check system resources and ensure there’s enough memory and disk space for the transform to run. Also, check for any potential bugs in the transform code that may be causing it to abort.
This guide will help you check for common problems that cause the log ” [{}] data frame transform received abort request. Stopping indexer. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request, plugin.
Log Context
Log “[{}] data frame transform received abort request. Stopping indexer.” classname is DataFrameTransformTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
@Override
protected void onAbort() {
auditor.info(transformConfig.getId(); "Received abort request; stopping data frame transform.");
logger.info("[{}] data frame transform received abort request. Stopping indexer."; transformConfig.getId());
transformTask.shutdown();
}
@Override
protected void createCheckpoint(ActionListener listener) {
[ratemypost]
