Log Cluster_shutdown requested. shutting down in – How To Solve Related Issues


Log Cluster_shutdown requested. shutting down in – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Cluster_shutdown requested. shutting down in ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: admin, cluster and node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[cluster_shutdown]: requested; shutting down in [{}]” classname is TransportNodesShutdownAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (disabled) {
            throw new ElasticsearchIllegalStateException("Shutdown is disabled");
        }
        final ObjectOpenHashSet nodes = new ObjectOpenHashSet();
        if (state.nodes().isAllNodes(request.nodesIds)) {
            logger.info("[cluster_shutdown]: requested; shutting down in [{}]"; request.delay);
            nodes.addAll(state.nodes().dataNodes().values());
            nodes.addAll(state.nodes().masterNodes().values());
            Thread t = new Thread(new Runnable() {
                
Override
                public void run() {



 

Optimize Elasticsearch Performance

Try The Tool