How To Solve Issues Related to Log – Restarting in

How To Solve Issues Related to Log – Restarting in

Updated: Feb-20

Elasticsearch Version: 1.7-8.0


Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.

To troubleshoot log “Restarting in” 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”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) {

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 Restart elasticsearch node

69.99 K 53

Restart Elasticsearch Node  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now