Briefly, this error occurs when Elasticsearch is unable to find or load the specified types. This could be due to incorrect type names, missing data, or configuration issues. To resolve this, ensure that the type names are correct and the data associated with these types exist. If the issue persists, check your Elasticsearch configuration for any inconsistencies or errors. You may also need to reindex your data if it’s not properly indexed.
This guide will help you check for common problems that cause the log ” no ” + type + “s loaded ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins.
Log Context
Log “no ” + type + “s loaded” classname is PluginsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
private static void logPluginInfo(final List pluginDescriptors; final String type; final Logger logger) {
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 + "]");
}
}
