# Node lock error in elasticsearch

**URL:** <https://discuss.elastic.co/t/node-lock-error-in-elasticsearch/164133>\
**Category:** Elasticsearch\
**Created:** [January 14, 2019, 11:53am UTC](https://discuss.elastic.co/t/node-lock-error-in-elasticsearch/164133 "2019-01-14T11:53:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![natey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/natey/32/61112_2.png) [@natey](https://discuss.elastic.co/u/natey)\
**Post date:** [January 14, 2019, 11:53am UTC](https://discuss.elastic.co/t/node-lock-error-in-elasticsearch/164133/1 "2019-01-14T11:53:32Z")

</div>

I installed ES 5.1.1 on cluster of 3 nodes , while kept almost all configurations as default.  
when trying to upgrade ES to 5.5.0 I get this WARN:

[WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] uncaught exception in thread [main]  
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[/opt/elasticsearch-5.5.0/data/elasticsearch]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max\_local\_storage\_nodes] (was [1])?

The only solution so far is to erase elastic volume after using ES 5.1 and recreate it when upgrade to 5.5 .  
Is there any way to overcome this problem without losing data?

---

<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:** [February 11, 2019, 11:53am UTC](https://discuss.elastic.co/t/node-lock-error-in-elasticsearch/164133/2 "2019-02-11T11:53:34Z")

</div>

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