Registry miss-match – expected RangeAggregatorSupplier 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 aggregator in Elasticsearch. This usually happens due to incorrect configuration or version incompatibility. To resolve this issue, you can try the following: 1) Check your Elasticsearch configuration and ensure it matches with the expected aggregator. 2) Verify if you’re using the correct version of Elasticsearch that supports the RangeAggregatorSupplier. 3) If you’ve recently upgraded Elasticsearch, ensure all nodes are upgraded and restarted properly. 4) Check your custom plugins or scripts, if any, for compatibility issues.

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