Removing shutdown record for node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.16-8.9

Briefly, this error occurs when Elasticsearch is shutting down a node and removing its record from the cluster. This could be due to a planned shutdown, a node failure, or network issues. To resolve this, ensure the node is properly shut down before removing it. If it’s a node failure, check the logs for any issues and fix them. If it’s a network issue, ensure the network connectivity between the nodes is stable. Also, consider setting up a monitoring system to track the health of your Elasticsearch cluster.

This guide will help you check for common problems that cause the log ” removing shutdown record for node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node.

Log Context

Log “removing shutdown record for node [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (shutdownMetadata.containsKey(request.getNodeId()) == false) {
            // noop; the node has already been removed by the time we got to this update task
            return false;
        }"removing shutdown record for node [{}]"; request.getNodeId());
        return true;

    private static void ackAndReroute(Request request; ActionListener listener; RerouteService rerouteService) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?