Registry miss-match – expected MissingAggregatorSupplier; found – 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 ” Registry miss-match – expected MissingAggregatorSupplier; found ” 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 “Registry miss-match – expected MissingAggregatorSupplier; found [“classname  is MissingAggregatorFactory.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

boolean collectsFromSingleBucket;
 Map metadata) throws IOException {
 final AggregatorSupplier aggregatorSupplier = queryShardContext.getValuesSourceRegistry()
 .getAggregator(config; MissingAggregationBuilder.NAME);
 if (aggregatorSupplier instanceof MissingAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected MissingAggregatorSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 } 
 return ((MissingAggregatorSupplier) aggregatorSupplier).build(name; factories; config; searchContext; parent; metadata);
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content