Initiating requested shutdown using service – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch receives a request to shut down the service. This could be due to a manual shutdown command, or an automatic shutdown triggered by system processes like memory overload or disk space issues. To resolve this, ensure that the shutdown command was intentional. If not, investigate system logs to identify any issues that may have triggered the shutdown. Also, check the system resources like memory and disk space, and increase them if necessary. Regularly monitor the system to prevent such issues in the future.

This guide will help you check for common problems that cause the log ” initiating requested shutdown (using service) ” 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 “initiating requested shutdown (using service)” classname is TransportNodesShutdownAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
                    boolean shutdownWithWrapper = false;
                    if (System.getProperty("elasticsearch-service") != null) {
                        try {
                            Class wrapperManager = settings.getClassLoader().loadClass("org.tanukisoftware.wrapper.WrapperManager");
                            logger.info("initiating requested shutdown (using service)");
                            wrapperManager.getMethod("stopAndReturn"; int.class).invoke(null; 0);
                            shutdownWithWrapper = true;
                        } catch (Throwable e) {
                            logger.error("failed to initial shutdown on service wrapper"; e);
                        }

 

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?