Shutting down in – How to solve related issues

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 run 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 ” 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 “shutting down in [{}]” classname is TransportNodesShutdownAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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


 

Run the Check-Up to get a customized report like this:

Analyze your cluster