Failed to shutdown – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch encounters issues while attempting to shut down, possibly due to ongoing processes or locked resources. To resolve this, you can try to identify and stop any ongoing processes or tasks before attempting to shut down. If the issue persists, you may need to manually kill the Elasticsearch process. However, this should be a last resort as it can potentially lead to data loss. Always ensure to backup your data regularly to prevent any loss.

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

Log Context

Log “Failed to shutdown” classname is TransportNodesShutdownAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     if (!request.exit) {
                        logger.info("initiating requested shutdown (no exit)...");
                        try {
                            node.close();
                        } catch (Exception e) {
                            logger.warn("Failed to shutdown"; e);
                        }
                        return;
                    }
                    boolean shutdownWithWrapper = false;
                    if (System.getProperty("elasticsearch-service") != null) {




 

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?