Uncaught exception when notifying plugins of nodes shutdown – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.14-8.2

Briefly, this error occurs when Elasticsearch encounters an unexpected issue while notifying plugins about the shutdown of nodes. This could be due to a variety of reasons such as a faulty plugin, network issues, or insufficient resources. To resolve this issue, you could try the following: 1) Check and update or fix any faulty plugins. 2) Ensure that there are sufficient resources available for Elasticsearch to operate. 3) Check the network connectivity between the nodes and plugins. 4) Review the Elasticsearch logs for more detailed information about the error.

This guide will help you check for common problems that cause the log ” uncaught exception when notifying plugins of nodes {} shutdown ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins.

Log Context

Log “uncaught exception when notifying plugins of nodes {} shutdown” classname is PluginShutdownService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        Set shutdownNodes = shutdownNodes(state);
        for (ShutdownAwarePlugin plugin : plugins) {
            try {
            } catch (Exception e) {
                logger.warn(new ParameterizedMessage("uncaught exception when notifying plugins of nodes {} shutdown"; shutdownNodes); e);



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?