Aggregation ” + + ” cannot have a global ” + “sub-aggregation – 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 ” Aggregation ” + + ” cannot have a global ” + “sub-aggregation ” 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 “Aggregation [” + + “] cannot have a global ” + “sub-aggregation [“classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public Aggregator createInternal(SearchContext searchContext;
 Aggregator parent;
 boolean collectsFromSingleBucket;
 Map metadata) throws IOException {
 if (parent != null) {
 throw new AggregationExecutionException("Aggregation [" + + "] cannot have a global " + "sub-aggregation [" + name
 + "]. Global aggregations can only be defined as top level aggregations");
 if (collectsFromSingleBucket == false) {
 throw new IllegalStateException();


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