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

Opster Team

August-23, Version: 7.8-7.9

Briefly, this error occurs when there’s a mismatch between the expected and found metric aggregator supplier in Elasticsearch. This could be due to a version mismatch or incorrect configuration. To resolve this issue, you can try the following: 1) Ensure that all nodes in your Elasticsearch cluster are running the same version. 2) Check your Elasticsearch configuration for any errors or inconsistencies. 3) If you’re using custom plugins, ensure they’re compatible with your Elasticsearch version. 4) If the error persists, consider a full cluster restart after taking a backup.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected MetricAggregatorSupplier; 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 MetricAggregatorSupplier; 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;
 StatsAggregationBuilder.NAME);  if (aggregatorSupplier instanceof MetricAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected MetricAggregatorSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 return ((MetricAggregatorSupplier) aggregatorSupplier).build(name; config; searchContext; parent; 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?