Plugin implementing onModule by the type is not of Module type – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when an Elasticsearch plugin is incorrectly implemented. The plugin is trying to use the onModule method, but the type it’s using is not of the Module type. To resolve this issue, you can check the plugin’s code to ensure that the correct type is being used. If the type is correct, ensure that the plugin is compatible with your version of Elasticsearch. If it’s not, you may need to update your Elasticsearch version or find a different plugin that is compatible.

This guide will help you check for common problems that cause the log ” Plugin: {} implementing onModule by the type is not of Module type {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins.

Log Context

Log “Plugin: {} implementing onModule by the type is not of Module type {}” classname is PluginsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

logger.warn("Plugin: {} implementing onModule with no parameters or more than one parameter"; plugin.name());
                    continue;
                }
                Class moduleClass = method.getParameterTypes()[0];
                if (!Module.class.isAssignableFrom(moduleClass)) {
                    logger.warn("Plugin: {} implementing onModule by the type is not of Module type {}"; plugin.name(); moduleClass);
                    continue;
                }
                list.add(new OnModuleReference(moduleClass; method));
            }
            if (!list.isEmpty()) {

 

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?