Starting cluster manager throttling as all nodes are higher than or equal to 2.5.0 – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 2.5-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 all nodes in your OpenSearch cluster are running a version that is 2.5.0 or higher. This triggers the cluster manager to start throttling, which can slow down operations. To resolve this issue, you can consider downgrading some of your nodes to a version lower than 2.5.0. Alternatively, you can adjust the cluster settings to handle higher version nodes without throttling. Lastly, ensure that your applications and queries are optimized for efficiency to reduce the load on the cluster.

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 ” Starting cluster manager throttling as all nodes are higher than or equal to 2.5.0 ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: cluster.

Log Context

Log “Starting cluster manager throttling as all nodes are higher than or equal to 2.5.0” classname is ClusterManagerTaskThrottler.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

     */
    private boolean shouldThrottle(Long threshold; Long count; int size) {
        if (!startThrottling.get()) {
            if (minNodeVersionSupplier.get().compareTo(Version.V_2_5_0) >= 0) {
                startThrottling.compareAndSet(false; true);
                logger.info("Starting cluster manager throttling as all nodes are higher than or equal to 2.5.0");
            } else {
                logger.info("Skipping cluster manager throttling as at least one node 

 

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