# Obtaining shard lock for \[read metadata snapshot\] timed out after \[5000ms\], lock already held for \[closing shard\] with age \[24721ms\]"

**URL:** <https://discuss.elastic.co/t/obtaining-shard-lock-for-read-metadata-snapshot-timed-out-after-5000ms-lock-already-held-for-closing-shard-with-age-24721ms/312169>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [August 16, 2022, 10:27am UTC](https://discuss.elastic.co/t/obtaining-shard-lock-for-read-metadata-snapshot-timed-out-after-5000ms-lock-already-held-for-closing-shard-with-age-24721ms/312169 "2022-08-16T10:27:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RaviS](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@RaviS](https://discuss.elastic.co/u/RaviS)\
**Post date:** [August 16, 2022, 10:27am UTC](https://discuss.elastic.co/t/obtaining-shard-lock-for-read-metadata-snapshot-timed-out-after-5000ms-lock-already-held-for-closing-shard-with-age-24721ms/312169/1 "2022-08-16T10:27:24Z")

</div>

obtaining shard lock for [read metadata snapshot] timed out after [5000ms], lock already held for [closing shard] with age [24721ms]"

Is there any reason for this message ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 17, 2022, 3:39am UTC](https://discuss.elastic.co/t/obtaining-shard-lock-for-read-metadata-snapshot-timed-out-after-5000ms-lock-already-held-for-closing-shard-with-age-24721ms/312169/2 "2022-08-17T03:39:25Z")

</div>

It'd be useful if you could share the entire log entry please.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 14, 2022, 3:40am UTC](https://discuss.elastic.co/t/obtaining-shard-lock-for-read-metadata-snapshot-timed-out-after-5000ms-lock-already-held-for-closing-shard-with-age-24721ms/312169/3 "2022-09-14T03:40:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.