How To Solve Issues Related to Log – Shutting down in

How To Solve Issues Related to Log – Shutting down in

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Shutting down in” it’s important to understand a few problems related to Elasticsearch concepts admin, cluster, node. See bellow important tips and explanations on these concepts

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());


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How to stop

95.92 K 78

Elasticsearch Gets Shut Down Automa  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now