Closing – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is in the process of shutting down or has already shut down. This could be due to a manual shutdown command, a crash due to an error, or a system failure. To resolve this issue, you can check the Elasticsearch logs for any errors that may have caused a crash. If it was a manual shutdown, simply restart Elasticsearch. If it’s a system failure, you may need to investigate further into your system’s health and resources. If the error persists, consider checking your cluster’s health or reconfiguring your Elasticsearch settings.

This guide will help you check for common problems that cause the log ” closing … ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Log Context

Log “closing …” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            if (lifecycle.moveToClosed() == false) {
        }"closing ...");
        List toClose = new ArrayList();
        StopWatch stopWatch = new StopWatch("node_close");
        toClose.add(() -> stopWatch.start("node_service"));
        toClose.add(() -> stopWatch.stop().start("http"));


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?