Restarting in – How to solve related issues

Restarting in – 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 ” Restarting in ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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) {


Run the Check-Up to get a customized report like this:

Analyze your cluster