# Understanding node.max\_local\_storage\_nodes?

**URL:** <https://discuss.elastic.co/t/understanding-node-max-local-storage-nodes/332682>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [May 5, 2023, 9:40pm UTC](https://discuss.elastic.co/t/understanding-node-max-local-storage-nodes/332682 "2023-05-05T21:40:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lakh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lakh/32/120713_2.png) [@lakh](https://discuss.elastic.co/u/lakh)\
**Post date:** [May 5, 2023, 9:40pm UTC](https://discuss.elastic.co/t/understanding-node-max-local-storage-nodes/332682/1 "2023-05-05T21:40:22Z")

</div>

Hi, my setup is that I have multiple people running their own docker containers on different machines that have access to shared storage. I've put the `elasticsearch-` folder in that shared location (so the `/data/index` folder is there too), with the goal of allowing different users to work off of the same index. But, out of the box, if two users try to run elastic, we get the `failed to obtain node locks` error. We are not in a production environment and we will have a small number of users (maybe max 10) using any given index at the same time).

Can fix this error and allow multiple users to query the index by setting `node.max_local_storage=N` (where N \> 1) in `elasticsearch.yaml`? If not, which setting am I looking for?

Am I understanding `node.max_local_storage` correctly? Are there any issues with setting `node.max_local_storage` \> 1?

---

<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:** [May 8, 2023, 2:51am UTC](https://discuss.elastic.co/t/understanding-node-max-local-storage-nodes/332682/2 "2023-05-08T02:51:05Z")

</div>

Welcome to our community! 😃

TDLR - this will not work in Elasticsearch 8.X because multiple nodes cannot write to the same directory in this way. See [Node | Elasticsearch Guide [7.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/modules-node.html#max-local-storage-nodes) (emphasis mine);

> `node.max_local_storage_nodes` [edit](https://github.com/elastic/elasticsearch/edit/7.17/docs/reference/modules/node.asciidoc)
> 
> The [data path](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/modules-node.html#data-path) can be shared by multiple nodes, even by nodes from different clusters. It is recommended however to only run one node of Elasticsearch using the same data path. **This setting is deprecated in 7.x and will be removed in version 8.0.**

> [@lakh](#):
>
> with the goal of allowing different users to work off of the same index

> [@lakh](#):
>
> I have multiple people running their own docker containers on different machines

Can you not run a single persistent container that lets your users access the Elasticsearch APIs instead?

---

<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:** [June 5, 2023, 2:51am UTC](https://discuss.elastic.co/t/understanding-node-max-local-storage-nodes/332682/3 "2023-06-05T02:51:15Z")

</div>

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