Reload failed for plugin – How to solve related issues

Average Read Time

2 Mins

Reload failed for plugin – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Reload failed for plugin ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, cluster, node, plugin and settings.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Reload failed for plugin [{}]” classname is TransportNodesReloadSecureSettingsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             // broadcast the new settings object (with the open embedded keystore) to all reloadable plugins
            pluginsService.filterPlugins(ReloadablePlugin.class).stream().forEach(p -> {
                try {
                    p.reload(settingsWithKeystore);
                } catch (final Exception e) {
                    logger.warn((Supplier>) () -> new ParameterizedMessage("Reload failed for plugin [{}]"; p.getClass().getSimpleName());
                            e);
                    exceptions.add(e);
                }
            });
            ExceptionsHelper.rethrowAndSuppress(exceptions);




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content