Registry miss-match – expected – How to solve this Elasticsearch error

Registry miss-match – expected – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: search and aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”Registry miss-match – expected”classname  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 MetricAggregatorSupplier == false) {
  throw new AggregationExecutionException("Registry miss-match - expected "
  + MetricAggregatorSupplier.class.getName() + "; found [" + aggregatorSupplier.getClass().toString() + "]");
  return ((MetricAggregatorSupplier) aggregatorSupplier).build(name; config; searchContext; parent; metadata);


Run the Check-Up to get a customized report like this:

Analyze your cluster