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

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch encounters an issue while bootstrapping with a voting configuration. This could be due to a network issue, a misconfiguration, or a problem with the cluster state. To resolve this issue, you can try the following: 1) Check your network connectivity and firewall settings to ensure nodes can communicate properly. 2) Review your Elasticsearch configuration for any errors or inconsistencies. 3) Check the cluster state and ensure all nodes are functioning correctly. 4) If the problem persists, consider restarting your Elasticsearch cluster.

This guide will help you check for common problems that cause the log ” exception when bootstrapping with ” + votingConfiguration + “; 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 ” + votingConfiguration + “; 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(() -> "exception when bootstrapping with " + votingConfiguration + "; rescheduling"; 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?