Not all shards are closed yet; waited sec stopping service – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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 and shards.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Not all shards are closed yet; waited {}sec – stopping service” classname is IndicesService.java.
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 {
            indicesStopExecutor.shutdown();




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content