Log no shard lock for pending delete – How To Solve Related Issues

Log no shard lock for pending delete – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “no shard lock for pending delete” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: delete, indices, shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”{} no shard lock for pending delete” classname is IndicesService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                } catch (IOException ex) {
                                    logger.debug(() -> new ParameterizedMessage("{} retry pending delete"; shardLock.getShardId()); ex);
                            } else {
                                logger.warn("{} no shard lock for pending delete"; delete.shardId);
                    if (remove.isEmpty() == false) {


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 ElasticSearch: Unassigned Shards, how to fix? -views 203.11 K ,score 152

Github Issue Number 14932  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now