# Elasticsearch V5 is looking for cluster\_name folder for data path

**URL:** <https://discuss.elastic.co/t/elasticsearch-v5-is-looking-for-cluster-name-folder-for-data-path/111244>\
**Category:** Elasticsearch\
**Created:** [December 12, 2017, 6:38am UTC](https://discuss.elastic.co/t/elasticsearch-v5-is-looking-for-cluster-name-folder-for-data-path/111244 "2017-12-12T06:38:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gayathri](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@gayathri](https://discuss.elastic.co/u/gayathri)\
**Post date:** [December 12, 2017, 6:38am UTC](https://discuss.elastic.co/t/elasticsearch-v5-is-looking-for-cluster-name-folder-for-data-path/111244/1 "2017-12-12T06:38:25Z")

</div>

Hi Team,

As per: [https://www.elastic.co/guide/en/elasticsearch/reference/5.2/\_path\_to\_data\_on\_disk.html#\_local\_files](https://www.elastic.co/guide/en/elasticsearch/reference/5.2/_path_to_data_on_disk.html#_local_files)

Our elasticsearch was working fine and it was storing index on path: $DATA\_DIR/nodes/$nodeOrdinal

But suddenly it's down with the below error:

java.lang.IllegalStateException: failed to obtain node locks, tried [[DATA\_DIR/Cluster\_E3]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max\_local\_storage\_nodes] (was [1])?

It's searching for the cluster named folder, which was not happend before and there are no such folder inside DATA\_DIR

Elasticsearch- version 5.0.2

Thanks,

Gayathri

---

<div class="post-metadata">

**Author:** ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)\
**Post date:** [December 15, 2017, 10:55am UTC](https://discuss.elastic.co/t/elasticsearch-v5-is-looking-for-cluster-name-folder-for-data-path/111244/2 "2017-12-15T10:55:52Z")

</div>

what you see is just the error message that it tried to use the path with the cluster name since that is how 2.x worked. This is only there for backwards compatibility. Did you maybe still have an ES instance running on that node / datadir?

---

<div class="post-metadata">

**Author:** ![gayathri](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@gayathri](https://discuss.elastic.co/u/gayathri)\
**Post date:** [December 21, 2017, 7:01am UTC](https://discuss.elastic.co/t/elasticsearch-v5-is-looking-for-cluster-name-folder-for-data-path/111244/3 "2017-12-21T07:01:32Z")

</div>

"No. only one instance is running on that server. And it was working fine before. Suddenly started looking for the old path after a restart..

---

<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:** [January 18, 2018, 7:02am UTC](https://discuss.elastic.co/t/elasticsearch-v5-is-looking-for-cluster-name-folder-for-data-path/111244/4 "2018-01-18T07:02:14Z")

</div>

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