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

Opster Team

Aug-23, Version: 1-2.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 OpenSearch operation.

Briefly, this error occurs when OpenSearch is trying to close all shards during a shutdown or restart process, but some shards are still open even after waiting for a specified period. This could be due to slow network, heavy load, or unresponsive nodes. To resolve this, you can increase the timeout period to allow more time for the shards to close. Alternatively, you can investigate the cause of the delay, such as checking for network issues or overloaded nodes. If a specific shard is consistently problematic, consider relocating it or checking it for corruption.

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 OpenSearch concepts: shards, indices.

Log Context

Log “Not all shards are closed yet; waited {}sec – stopping service” classname is
We extracted the following from OpenSearch 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