Registry miss-match – expected ExtendedStatsAggregatorProvider found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.9-7.9

Briefly, this error occurs when there’s a mismatch between the expected and found aggregators in Elasticsearch. This could be due to incorrect configuration or version incompatibility. To resolve this, you can try the following: 1) Check and correct your Elasticsearch configuration, ensuring that the correct aggregators are being used. 2) Verify that all components of your Elasticsearch cluster are running the same version. 3) If you’ve recently upgraded Elasticsearch, ensure that all plugins and dependencies are compatible with the new version.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected ExtendedStatsAggregatorProvider; found [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Log Context

Log “Registry miss-match – expected ExtendedStatsAggregatorProvider; found [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 Map metadata) throws IOException {
 AggregatorSupplier aggregatorSupplier = queryShardContext.getValuesSourceRegistry().getAggregator(config;
 ExtendedStatsAggregationBuilder.NAME);  if (aggregatorSupplier instanceof ExtendedStatsAggregatorProvider == false) {
 throw new AggregationExecutionException("Registry miss-match - expected ExtendedStatsAggregatorProvider; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 return new ExtendedStatsAggregator(name; config; searchContext; parent; sigma; metadata);


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?