No shard lock for pending delete – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch tries to delete a shard that is currently in use or locked by another process. This could be due to a concurrent indexing or search operation. To resolve this issue, you can try the following: 1) Wait for the ongoing operations to complete before attempting the delete operation again. 2) Restart the Elasticsearch node to clear any lingering locks. 3) Check for any issues with your cluster health and resolve them. Always ensure that your operations are not conflicting with each other to avoid such 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: indices, delete, shard.

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(() -> format("%s retry pending delete"; shardLock.getShardId()); ex);
                            } else {
                                logger.warn("{} no shard lock for pending delete"; delete.shardId);
                    if (remove.isEmpty() == false) {


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?