Shutting down in – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch is either manually shut down or encounters a critical issue that forces it to shut down. This could be due to insufficient memory, disk space, or a configuration error. To resolve this, ensure that your system has enough resources (RAM, disk space) to run Elasticsearch. Check your Elasticsearch configuration for any errors. If the shutdown was manual, simply restarting Elasticsearch might solve the issue. If the problem persists, check the Elasticsearch logs for more detailed error messages that can help identify the root cause.

This guide will help you check for common problems that cause the log ” shutting down in [{}] ” 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 “shutting down in [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        public void messageReceived(final NodeShutdownRequest request; TransportChannel channel) throws Exception {
            if (disabled) {
                throw new ElasticsearchIllegalStateException("Shutdown is disabled");
  "shutting down in [{}]"; delay);
            Thread t = new Thread(new Runnable() {
                public void run() {
                    try {


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?