Exception when bootstrapping with rescheduling – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7-8.2

Briefly, this error occurs when Elasticsearch encounters an issue during the bootstrapping process, which could be due to a variety of reasons such as insufficient resources, network connectivity issues, or configuration errors. To resolve this issue, you can try the following: 1) Check if the system has enough resources (CPU, memory, disk space). 2) Verify the network connectivity between the nodes. 3) Review the Elasticsearch configuration for any errors or inconsistencies. 4) Check the Elasticsearch logs for more detailed error messages that can help pinpoint the exact issue.

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


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?