Briefly, this error occurs when Elasticsearch encounters an issue during the shutdown process. This could be due to a variety of reasons such as unresponsive nodes, ongoing tasks, or system resource issues. To resolve this, you can try to manually stop the unresponsive nodes, ensure all tasks are completed before shutting down, or increase system resources. Additionally, checking the Elasticsearch logs can provide more detailed information about the cause of the error.
This guide will help you check for common problems that cause the log ” [{}] Failed to stop normally ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] Failed to stop normally” classname is TransportDeleteDataFrameAnalyticsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
parentTaskClient;
ML_ORIGIN;
StopDataFrameAnalyticsAction.INSTANCE;
stopRequest;
ActionListener.wrap(listener::onResponse; forceStopFailure -> {
logger.error(new ParameterizedMessage("[{}] Failed to stop normally"; request.getId()); normalStopFailure);
logger.error(new ParameterizedMessage("[{}] Failed to stop forcefully"; request.getId()); forceStopFailure);
listener.onFailure(forceStopFailure);
})
);
}
[ratemypost]
