Initiating requested shutdown no exit – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch is requested to shut down. It’s a normal part of the shutdown process and not an error per se. However, if this happens unexpectedly, it could be due to issues like insufficient resources, configuration errors, or external system commands. To resolve this, ensure your system has enough resources (CPU, memory, disk space), check your Elasticsearch configuration for any errors, and monitor external system activities that may be triggering the shutdown. Also, consider setting up proper logging and monitoring to identify any potential issues early.

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

                    } catch (InterruptedException e) {
                        // ignore
                    if (!request.exit) {
              "initiating requested shutdown (no exit)...");
                        try {
                        } catch (Exception e) {
                            logger.warn("Failed to shutdown"; 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?