Loaded type name – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.7

Briefly, this error occurs when Elasticsearch encounters a type name that has already been loaded or defined. This could be due to a duplicate type name in the mappings or a conflict in the type names across different indices. To resolve this issue, you can either rename the duplicate type name or delete and recreate the index with a unique type name. Additionally, ensure that the type names across different indices do not conflict.

This guide will help you check for common problems that cause the log ” loaded ” + type + ” [” + name + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins.

Log Context

Log “loaded ” + type + ” [” + name + “]” classname is PluginsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        assert pluginDescriptors != null;
        if (pluginDescriptors.isEmpty()) {
            logger.info("no " + type + "s loaded");
        } else {
            for (final String name : pluginDescriptors.stream().map(PluginDescriptor::getName).sorted().toList()) {
                logger.info("loaded " + type + " [" + name + "]");

    private static List getRuntimeInfos(


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?