How To Solve Issues Related to Log – Not all shards are closed yet; waited sec stopping service

How To Solve Issues Related to Log – Not all shards are closed yet; waited sec stopping service

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Not all shards are closed yet; waited sec stopping service” it’s important to understand a few problems related to Elasticsearch concepts indices, shards. See bellow important tips and explanations on these concepts

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();




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How to stop

91.96 K 75

Github Issue Number 10680  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now