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

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch tries to delete a shard that is currently not locked or is being used by another process. This could be due to a synchronization issue or a bug in the system. To resolve this issue, you can try restarting the OpenSearch service to clear any locks. If the problem persists, you may need to manually unlock the shard or check for any processes that may be using the shard and stop them. Always ensure to backup your data before performing these operations to prevent data loss.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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 OpenSearch concepts: delete, indices, shard.

Log Context

Log “{} no shard lock for pending delete” classname is
We extracted the following from OpenSearch 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) {


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?

Get expert answers on Elasticsearch/OpenSearch