Updating existing shutdown record with new record – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.16-8.9

Briefly, this error occurs when Elasticsearch tries to update an existing shutdown record with a new one. This usually happens when a node is being shut down while it’s still processing requests. To resolve this issue, you can try the following: 1) Ensure that all requests are completed before shutting down a node. 2) Check the cluster health and make sure all nodes are functioning properly before initiating a shutdown. 3) If the error persists, consider increasing the timeout period to allow more time for requests to complete before shutdown.

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

Log Context

Log “updating existing shutdown record {} with new record {}” classname is TransportPutShutdownNodeAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        // log the update
        SingleNodeShutdownMetadata existingRecord = shutdownMetadata.get(request.getNodeId());
        if (existingRecord != null) {
            logger.info("updating existing shutdown record {} with new record {}"; existingRecord; newNodeMetadata);
        } else {
            logger.info("creating shutdown record {}"; newNodeMetadata);

        shutdownMetadata.put(request.getNodeId(); newNodeMetadata);