Briefly, this error occurs when Elasticsearch is trying to refresh the memory of an anomaly detector while the node is in the process of shutting down. This could be due to a manual shutdown or an unexpected failure. To resolve this issue, ensure that the node is fully operational before running the job. If the problem persists, consider increasing the node’s memory or reducing the size of the job. Additionally, check for any network issues that might be causing the node to shut down unexpectedly.
This guide will help you check for common problems that cause the log ” [” + jobId + “] not refreshing anomaly detector memory as node is shutting down ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, memory, node.
Overview
To put it simply, a node is a single server that is part of a cluster. Each node is assigned one or more roles, which describe the node’s responsibility and operations. Data nodes store the data, and participate in the cluster’s indexing and search capabilities, while master nodes are responsible for managing the cluster’s activities and storing the cluster state, including the metadata.
While it is possible to run several node instances of Elasticsearch on the same hardware, it’s considered a best practice to limit a server to a single running instance of Elasticsearch.
Nodes connect to each other and form a cluster by using a discovery method.
Roles
Master node
Master nodes are in charge of cluster-wide settings and changes – deleting or creating indices and fields, adding or removing nodes and allocating shards to nodes. Each cluster has a single master node that is elected from the master eligible nodes using a distributed consensus algorithm and is reelected if the current master node fails.
Coordinating (client) node
There is some confusion in the use of coordinating node terminology. Client nodes were removed from Elasticsearch after version 2.4 and became coordinating nodes.
Coordinating nodes are nodes that do not hold any configured role. They don’t hold data and are not part of the master eligible group nor execute ingest pipelines. Coordinating nodes serve incoming search requests and act as the query coordinator running query and fetch phases, sending requests to every node that holds a shard being queried. The coordinating node also distributes bulk indexing operations and route queries to shards based on the node’s responsiveness.
Log Context
Log “[” + jobId + “] not refreshing anomaly detector memory as node is shutting down” classname is MlMemoryTracker.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// The phaser prevents searches being started after the memory tracker's stop() method has returned
// Note: `phase` is incremented if cache is reset via the feature reset API
if (stopPhaser.register() != phase.get()) {
// Phases above not equal to `phase` mean we've been stopped; so don't do any operations that involve external interaction
stopPhaser.arriveAndDeregister();
logger.info(() -> "[" + jobId + "] not refreshing anomaly detector memory as node is shutting down");
listener.onFailure(new EsRejectedExecutionException("Couldn't run ML memory update - node is shutting down"));
return;
}
ActionListener phaserListener = ActionListener.wrap(r -> {
stopPhaser.arriveAndDeregister();
