Found two aggregation type definitions in – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Found two aggregation type definitions in ” to appear. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Found two aggregation type definitions in [“classname  is AggregatorFactories.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 subFactories = parseAggregators(parser; level + 1);
 break;
 default:
 if (aggBuilder != null) {
 throw new ParsingException(parser.getTokenLocation(); "Found two aggregation type definitions in ["
 + aggregationName + "]: [" + aggBuilder.getType() + "] and [" + fieldName + "]");
 } 
 try {
 aggBuilder = parser.namedObject(BaseAggregationBuilder.class; fieldName; aggregationName);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content