Exception when bootstrapping with . rescheduling – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Exception when bootstrapping with . rescheduling ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap and cluster.

Log Context

Log “exception when bootstrapping with {}; rescheduling” classname is ClusterBootstrapService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         assert transportService.getLocalNode().isMasterNode();

        try {
        } catch (Exception e) {
            logger.warn(new ParameterizedMessage("exception when bootstrapping with {}; rescheduling"; votingConfiguration); e);
            transportService.getThreadPool().scheduleUnlessShuttingDown(TimeValue.timeValueSeconds(10); Names.GENERIC;
                new Runnable() {
                    public void run() {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content