Stopping – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is either manually stopped by a user or it encounters an issue that forces it to stop, such as a lack of system resources or a critical error. To resolve this, you can restart Elasticsearch, ensure there are sufficient system resources available, or check the Elasticsearch logs to identify and fix any critical errors. If the issue persists, you may need to reconfigure your Elasticsearch settings or even reinstall Elasticsearch.

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

Log Context

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

    private Node stop() {
        if (lifecycle.moveToStopped() == false) {
            return this;
        }"stopping ...");

        if (ReadinessService.enabled(environment)) {


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?