Log Initiating requested shutdown (no exit) – How To Solve Related Issues

Log Initiating requested shutdown (no exit) – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Initiating requested shutdown (no exit)” 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”initiating requested shutdown (no exit)…” classname is TransportNodesShutdownAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         Thread.sleep(delay.millis());
                    } catch (InterruptedException e) {
                        // ignore
                    }
                    if (!request.exit) {
                        logger.info("initiating requested shutdown (no exit)...");
                        try {
                            node.close();
                        } catch (Exception e) {
                            logger.warn("Failed to shutdown"; e);
                        }




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

do we need to close elasticsearch node after the every search request

  1.40 K 1

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now