Not all shards are closed yet waited sec – stopping service – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is trying to stop a service but some shards are still open. This could be due to a slow network, heavy indexing or search operations. To resolve this issue, you can increase the timeout settings, reduce the load on your Elasticsearch cluster by optimizing your indexing and search operations, or manually close the open shards before stopping the service. Also, ensure that your network is stable and fast enough to handle the data transfer between nodes.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Not all shards are closed yet; waited {}sec – stopping service ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, shards.

Log Context

Log “Not all shards are closed yet; waited {}sec – stopping service” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        try {
            if (latch.await(shardsClosedTimeout.seconds(); TimeUnit.SECONDS) == false) {
                logger.warn("Not all shards are closed yet; waited {}sec - stopping service"; shardsClosedTimeout.seconds());
        } catch (InterruptedException e) {
            // ignore
        } finally {


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?

Get expert answers on Elasticsearch/OpenSearch