Aggregation ” + name() + ” must have cardinality 1 but was ” + cardinality + ” – How to solve this Elasticsearch error

Average Read Time

2 Mins

Aggregation ” + name() + ” must have cardinality 1 but was ” + cardinality + ” – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Aggregation ” + name() + ” must have cardinality 1 but was ” + cardinality + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Aggregation [” + name() + “] must have cardinality 1 but was [” + cardinality + “]”classname  is GlobalAggregatorFactory.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

#ERROR!

 

Watch a demo of the Check-Up:

Analyze your cluster