Initiating requested restart – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch is manually restarted by a user or automatically by the system due to some internal issues like high memory usage, unresponsive nodes, or configuration changes. To resolve this, ensure that your system has enough resources to run Elasticsearch. Check for any unresponsive nodes and fix them. If the restart was due to configuration changes, verify that the changes are correct and necessary. Also, consider setting up monitoring and alerting to get notified about any issues before they cause a restart.

This guide will help you check for common problems that cause the log ” Initiating requested restart ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, cluster and node.

Log Context

Log “Initiating requested restart” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     } catch (Throwable e) {
                        logger.error("failed to initial restart on service wrapper"; e);
                if (!restartWithWrapper) {
          "Initiating requested restart");
                    try {
                    } catch (Exception e) {
                        logger.warn("Failed to restart"; e);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?