Aggregation ” + + ” cannot have a global ” + “sub-aggregation – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Aggregation ” + + ” cannot have a global ” + “sub-aggregation ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: search and aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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();


Run the Check-Up to get a customized report like this:

Analyze your cluster