%s failed to obtain shard lock – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch is unable to acquire a lock on a shard, usually due to concurrent operations on the same shard. This could be caused by a long-running operation, a node crash, or network issues. To resolve this, you can try the following: 1) Identify and stop any long-running operations on the shard. 2) Check for and resolve any network issues. 3) If a node has crashed, ensure it is properly restarted. 4) If the issue persists, you may need to perform a full cluster restart.

This guide will help you check for common problems that cause the log ” %s: failed to obtain shard lock ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, shard.

Log Context

Log “%s: failed to obtain shard lock” classname is Store.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        } catch (CorruptIndexException ex) {
            logger.info(() -> format("%s: corrupted"; shardId); ex);
        } catch (FileNotFoundException | NoSuchFileException ex) {
            logger.info("Failed to open / find files while reading metadata snapshot"; ex);
        } catch (ShardLockObtainFailedException ex) {
            logger.info(() -> format("%s: failed to obtain shard lock"; shardId); ex);
        return MetadataSnapshot.EMPTY;



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?