Unsupported database type – Elasticsearch Error How To Solve Related Issues


Unsupported database type – Elasticsearch Error How To Solve Related Issues

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 ” Unsupported database type ” 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: Node.

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”Unsupported database type [“classname  is GeoIpProcessor.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

geoData = retrieveAsnGeoData(ipAddress);
  } catch (AddressNotFoundRuntimeException e) {
  geoData = Collections.emptyMap();
  }
  } else {
  throw new ElasticsearchParseException("Unsupported database type [" + lazyLoader.getDatabaseType()
  + "]"; new IllegalStateException());
  }
  return geoData;
  }

 

Optimize Elasticsearch Performance

Try The Tool