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

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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 and thread.

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 “thread interrupted while trying to obtain shard lock”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

"obtaining shard lock timed out after " + timeoutInMillis + "ms; previous lock details: [" + lockDetails +
 "] trying to lock for [" + details + "]");
 } catch (InterruptedException e) {
 throw new ShardLockObtainFailedException(shardId; "thread interrupted while trying to obtain shard lock"; e);
 public boolean hasNodeFile() {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content