Registry miss-match – expected StringStatsAggregatorSupplier 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 actual type of AggregatorSupplier in Elasticsearch. This could be due to incorrect configuration or version incompatibility. To resolve this, you can try the following: 1) Check your Elasticsearch configuration for any errors. 2) Ensure that all nodes in your cluster are running the same version of Elasticsearch. 3) If you’re using any plugins, make sure they’re compatible with your Elasticsearch version. 4) If the error persists, consider upgrading or downgrading your Elasticsearch version.

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

Log Context

Log “Registry miss-match – expected StringStatsAggregatorSupplier; 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;
 StringStatsAggregationBuilder.NAME);  if (aggregatorSupplier instanceof StringStatsAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected StringStatsAggregatorSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 return ((StringStatsAggregatorSupplier) aggregatorSupplier).build(name; config.getValuesSource(); showDistribution; config.format();
 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?