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

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when a part of the Elasticsearch cluster is shut down. This could be due to a manual shutdown command, a node failure, or a network issue. To resolve this, you can restart the shut down nodes if they were manually shut down. If it’s a node failure, check the node’s logs to identify the issue and fix it. For network issues, ensure that all nodes are connected properly and the network is stable. Also, consider setting up a monitoring system to prevent such issues in the future.

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

                         latch.await();
                    } catch (InterruptedException e) {
                        // ignore
                    }

                    logger.info("[partial_cluster_shutdown]: done shutting down [{}]"; ((Object) nodesIds));
                }
            });
            t.start();
        }
        listener.onResponse(new NodesShutdownResponse(clusterName; nodes.toArray(DiscoveryNode.class)));




 

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?