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

Opster Team

August-23, Version: 7.8-7.9

Briefly, this error occurs when there is a mismatch between the expected and found aggregator in Elasticsearch. This usually happens when there is a version mismatch or a plugin compatibility issue. To resolve this, you can try updating Elasticsearch to the latest version or check if all plugins are compatible with your current version. If the error persists, you may need to remove and reinstall the plugin causing the issue. Also, ensure that your queries are correctly formatted and compatible with the version of Elasticsearch you are using.

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

 AggregatorSupplier aggregatorSupplier = queryShardContext.getValuesSourceRegistry().getAggregator(config;
 PercentilesAggregationBuilder.NAME);  if (aggregatorSupplier instanceof PercentilesAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected PercentilesAggregatorSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 PercentilesAggregatorSupplier percentilesAggregatorSupplier = (PercentilesAggregatorSupplier) aggregatorSupplier;


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?