Thread interrupted while trying to obtain shard lock – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when a thread in Elasticsearch is interrupted while trying to lock a shard for operations like indexing or searching. This could be due to high load, slow disk I/O, or a long garbage collection pause. To resolve this issue, you can optimize your queries to reduce load, upgrade your hardware for faster disk I/O, or adjust JVM settings to minimize garbage collection pauses. Additionally, ensure that your cluster is properly sized and not overloaded with too many shards.

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

Log Context

Log “thread interrupted while trying to obtain shard lock” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 maybeLogThreadDump(shardId; message);
 throw new ShardLockObtainFailedException(shardId; message);
 } catch (InterruptedException e) {
 throw new ShardLockObtainFailedException(shardId; "thread interrupted while trying to obtain shard lock"; e);
 }  public void setDetails(String details) {
 lockDetails = Tuple.tuple(System.nanoTime(); details);