Starting node shutdown sequence for ML – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.15-8.9

Briefly, this error occurs when Elasticsearch initiates a shutdown sequence for Machine Learning (ML) nodes. This could be due to a manual shutdown command, a system error, or resource constraints. To resolve this, you can restart the node if it was manually shut down. If it’s a system error, check the logs for more details and fix the underlying issue. If it’s due to resource constraints, consider scaling up your resources or optimizing your ML tasks to use less resources.

This guide will help you check for common problems that cause the log ” Starting node shutdown sequence for ML ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node.

Log Context

Log “Starting node shutdown sequence for ML” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    private void updateShutdownStartTimes(Collection shutdownNodeIds; String localNodeId; Clock clock) {
        for (String shutdownNodeId : shutdownNodeIds) {
            shutdownStartTimes.computeIfAbsent(shutdownNodeId; key -> {
                if (key.equals(localNodeId)) {
          "Starting node shutdown sequence for ML");