Restarting in – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch is either manually restarted or automatically restarted due to an internal issue such as a crash, memory overload, or configuration change. To resolve this, you can check the Elasticsearch logs for any error messages that might indicate the cause of the restart. If it’s a memory issue, consider increasing the heap size. If it’s due to a configuration change, review and correct the configuration. If the server is crashing, you might need to upgrade your server or Elasticsearch version.

This guide will help you check for common problems that cause the log ” Restarting in [{}] ” 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 “Restarting in [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             throw new ElasticsearchIllegalStateException("Restart is disabled");
        if (!restartRequested.compareAndSet(false; true)) {
            return new NodesRestartResponse.NodeRestartResponse(clusterService.localNode());
        }"Restarting in [{}]"; request.delay);
        threadPool.schedule(request.delay; ThreadPool.Names.GENERIC; new Runnable() {
            public void run() {
                boolean restartWithWrapper = false;
                if (System.getProperty("elasticsearch-service") != null) {


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?