Briefly, this error occurs when Elasticsearch successfully loads a module during its startup process. It’s not an error message but an informational log indicating that a specific module has been loaded correctly. If you’re seeing this frequently and it’s cluttering your logs, you can adjust your logging level to WARN or ERROR to see fewer informational messages. Alternatively, you can configure your logging settings to exclude these types of messages.
This guide will help you check for common problems that cause the log ” loaded module [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins.
Log Context
Log “loaded module [{}]” classname is PluginsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// we don't log jars in lib/ we really shouldn't log modules;
// but for now: just be transparent so we can debug any potential issues
for (String name : loadedPlugins.keySet()) {
if (moduleNameList.contains(name)) {
logger.info("loaded module [{}]"; name);
} else {
logger.info("loaded plugin [{}]"; name);
}
}
}
