Elected as master scheduling cluster info update tasks – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.3

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when a node in the OpenSearch cluster is elected as the master node and it schedules tasks to update the cluster information. This is not necessarily an error, but more of an informational message indicating the normal operation of the cluster. However, if you see this message frequently, it might indicate instability in the master election process. To resolve this, ensure all nodes are properly connected, check for network issues, and verify that your cluster has enough resources to prevent frequent master re-elections. Also, consider increasing the ‘discovery.zen.minimum_master_nodes’ setting to maintain stability.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” elected as master; scheduling cluster info update tasks ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: cluster.

Log Context

Log “elected as master; scheduling cluster info update tasks” classname is InternalClusterInfoService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :


    public void clusterChanged(ClusterChangedEvent event) {
        if (event.localNodeMaster() && refreshAndRescheduleRunnable.get() == null) {
            logger.trace("elected as master; scheduling cluster info update tasks");
            executeRefresh(event.state(); "became master");

            final RefreshAndRescheduleRunnable newRunnable = new RefreshAndRescheduleRunnable();
            threadPool.scheduleUnlessShuttingDown(updateFrequency; REFRESH_EXECUTOR; newRunnable);


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?

Get expert answers on Elasticsearch/OpenSearch