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

Opster Team

August-23, Version: 7.8-7.8

Briefly, this error occurs when there’s a mismatch between the expected and actual value in the Elasticsearch registry. 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 inconsistencies or errors. 3) If the error persists, consider reindexing your data. Always remember to backup your data before making any major changes.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected ValueCountAggregatorSupplier; 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 ValueCountAggregatorSupplier; found [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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