Encountered more than one weight for a – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Encountered more than one weight for a ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search and aggregations.


Log Context

Log “Encountered more than one weight for a”classname  is WeightedAvgAggregator.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

valueCompensations = bigArrays.grow(valueCompensations; bucket + 1);
 weightCompensations = bigArrays.grow(weightCompensations; bucket + 1); 
 if (docValues.advanceExact(doc) && docWeights.advanceExact(doc)) {
 if (docWeights.docValueCount() > 1) {
 throw new AggregationExecutionException("Encountered more than one weight for a " +
 "single document. Use a script to combine multiple weights-per-doc into a single value.");
 }
 // There should always be one weight if advanceExact lands us here; either
 // a real weight or a `missing` weight
 assert docWeights.docValueCount() == 1;

 

See how you can use AutoOps to resolve issues


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?

Analyze your cluster & get personalized recommendations

Skip to content