Initiating requested restart (using service) – How to solve related issues

Average Read Time

2 Mins

Initiating requested restart (using service) – 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 ” Initiating requested restart (using service) ” to appear. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Initiating requested restart (using service)” classname is TransportNodesRestartAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             public void run() {
                boolean restartWithWrapper = false;
                if (System.getProperty("elasticsearch-service") != null) {
                    try {
                        Class wrapperManager = settings.getClassLoader().loadClass("org.tanukisoftware.wrapper.WrapperManager");
                        logger.info("Initiating requested restart (using service)");
                        wrapperManager.getMethod("restartAndReturn").invoke(null);
                        restartWithWrapper = true;
                    } catch (Throwable e) {
                        logger.error("failed to initial restart on service wrapper"; e);
                    }




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster