Unknown exporter type ” + type + ” set for exporter ” + name + ” – How to solve this Elasticsearch error

Unknown exporter type ” + type + ” set for exporter ” + name + ” – 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 ” unknown exporter type ” + type + ” set for exporter ” + name + ” ” 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: plugin.

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”unknown exporter type [” + type + “] set for exporter [” + name + “]”classname  is Exporters.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (type == null) {
  throw new SettingsException("missing exporter type for [" + name + "] exporter");
  }
  Exporter.Factory factory = factories.get(type);
  if (factory == null) {
  throw new SettingsException("unknown exporter type [" + type + "] set for exporter [" + name + "]");
  }
  Exporter.Config config = new Exporter.Config(name; type; settings; clusterService; licenseState);
  if (!config.enabled()) {
  hasDisabled = true;
  if (logger.isDebugEnabled()) {

Run the Check-Up to get customized recommendations like this:

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized recommendation]

 

Optimize Elasticsearch Performance

Try The Tool