# Elasticsearch Failing. .kibana\_task\_manager\_8.5.0\_001 Failed engine index/write.lock

**URL:** <https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [March 29, 2023, 6:21am UTC](https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775 "2023-03-29T06:21:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![akansha.agarwal1](https://avatars.discourse-cdn.com/v4/letter/a/858c86/32.png) [@akansha.agarwal1](https://discuss.elastic.co/u/akansha.agarwal1)\
**Post date:** [March 29, 2023, 6:21am UTC](https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775/1 "2023-03-29T06:21:25Z")

</div>

Hi,

Version: 8.5.1  
currently I have a lot of trouble to keep the ELK alive.  
It failed twice exactly after 11 days.

I am using Elastic & Kibana on Kubernetes Rancher.  
Deployed single node cluster Using NFS as Persistent volume for the cluster.

Is the issue reoccuring when NFS storage is being used?  
If yes, is there any alternative for the same?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 29, 2023, 6:25am UTC](https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775/2 "2023-03-29T06:25:53Z")

</div>

> [@akansha.agarwal1](#):
>
> Is the issue reoccuring when NFS storage is being used?

Quite possibly. The [docs](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/modules-node.html#_node_data_path_settings) says the following:

> Elasticsearch requires the filesystem to act as if it were backed by a local disk, but this means that it will work correctly on properly-configured remote block devices (e.g. a SAN) and remote filesystems (e.g. NFS) as long as the remote storage behaves no differently from local storage.

---

<div class="post-metadata">

**Author:** ![akansha.agarwal1](https://avatars.discourse-cdn.com/v4/letter/a/858c86/32.png) [@akansha.agarwal1](https://discuss.elastic.co/u/akansha.agarwal1)\
**Post date:** [April 21, 2023, 8:49am UTC](https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775/3 "2023-04-21T08:49:58Z")

</div>

HI @Christian_Dahlqvist

Thanks for the reply!  
In that case, what is the recommended storage for ELK stack?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 21, 2023, 9:36am UTC](https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775/4 "2023-04-21T09:36:08Z")

</div>

Local SSDs are always recommended, which may not be an option in a k8s environment, but other types of storage are often used. It is usually fine as long as the guidance in the docs I linked to are followed.

---

<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:** [May 19, 2023, 9:36am UTC](https://discuss.elastic.co/t/elasticsearch-failing-kibana-task-manager-8-5-0-001-failed-engine-index-write-lock/328775/5 "2023-05-19T09:36:48Z")

</div>

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