Partial cluster shutdown requested shutting down in – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when a partial shutdown of the Elasticsearch cluster is initiated. This could be due to various reasons such as maintenance, updates, or resource allocation issues. To resolve this, ensure that all operations that could be affected by the shutdown are completed or paused. If the shutdown was unintentional, check the cluster settings and logs to identify what triggered it. If it’s due to resource issues, consider scaling up your cluster or optimizing your indices and queries to use resources more efficiently.

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

        } else {
            final String[] nodesIds = state.nodes().resolveNodesIds(request.nodesIds);
  "[partial_cluster_shutdown]: requested; shutting down [{}] in [{}]"; nodesIds; request.delay);

            for (String nodeId : nodesIds) {
                final DiscoveryNode node = state.nodes().get(nodeId);
                if (node != 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?