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 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 ” no shard lock for pending delete ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, indices and shard.

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 “{} no shard lock for pending delete” classname is
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) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content