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

Opster Team

Aug-23, Version: 2-2.9

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 cluster manager. This is not an error but an informational message indicating that the node is now responsible for scheduling and managing cluster info update tasks. If you’re seeing performance issues, it could be due to the cluster manager being overloaded. To resolve this, you can add more nodes to your cluster to distribute the load, or you can increase the resources (CPU, memory) available to the current cluster manager.

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 cluster-manager; 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 cluster-manager; 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.localNodeClusterManager() && refreshAndRescheduleRunnable.get() == null) {
            logger.trace("elected as cluster-manager; scheduling cluster info update tasks");
            executeRefresh(event.state(); "became cluster-manager");

            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