Weights are same not updating weighted routing weights in metadata – 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 OpenSearch tries to update the routing weights for shards but finds that the new weights are identical to the existing ones. This could be due to a configuration issue or a problem with the weight calculation. To resolve this, you can check your shard allocation settings and ensure they are correctly configured. If the problem persists, you may need to manually adjust the weights or investigate if there’s an issue with the weight calculation algorithm.

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 ” weights are same; not updating weighted routing weights [{}] in metadata ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: routing, cluster, metadata.

Log Context

Log “weights are same; not updating weighted routing weights [{}] in metadata” classname is WeightedRoutingService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                } else {
                    if (!newWeightedRouting.equals(weightedRoutingMetadata.getWeightedRouting())) {
                        logger.info("updated weighted routing weights [{}] in metadata"; newWeightedRouting);
                        weightedRoutingMetadata = new WeightedRoutingMetadata(newWeightedRouting; requestVersion + 1);
                    } else {
                        logger.info("weights are same; not updating weighted routing weights [{}] in metadata"; newWeightedRouting);
                        return currentState;
                mdBuilder.putCustom(WeightedRoutingMetadata.TYPE; weightedRoutingMetadata);
                logger.info("building cluster state with weighted routing weights [{}]"; newWeightedRouting);


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