# This node is locked **URL:** \ **Category:** Elasticsearch\ **Created:** [January 12, 2023, 3:40pm UTC](https://discuss.elastic.co/t/this-node-is-locked/323040 "2023-01-12T15:40:45Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Randomize](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Randomize](https://discuss.elastic.co/u/Randomize)\ **Post date:** [January 12, 2023, 3:40pm UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/1 "2023-01-12T15:40:45Z")
Hello I updated elasticsearch to version 8.4.1 Now im trying to start elasticsearch using discovery.type: single-node in config file. But its does not starting. I can see status activating in systemctl status. In elasticsearch.log i can see this message: > **Summary** > > [2023-01-12T18:23:23,740][WARN][o.e.c.c.ClusterBootstrapService] [node1] this node is locked into cluster UUID [nwFy-ImJTfy0iYUpOF32gh] but [cluster.initial\_master\_nodes] is set to [node1]; remove this setting to avoid possible data loss caused by subsequent cluster bootstrap attempts cluster.initial\_master\_nodes commented in elasticsearch.yml How can i fix this warning? How can i unlock node in cluster? ---
**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:** [January 12, 2023, 9:03pm UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/2 "2023-01-12T21:03:10Z")
Welcome to our community! 😃 Was this part of a multi-node cluster originally? ---
**Author:** ![weizijun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weizijun/32/115883_2.png) [@weizijun](https://discuss.elastic.co/u/weizijun)\ **Post date:** [January 13, 2023, 1:49am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/3 "2023-01-13T01:49:30Z")
> [@Randomize](#): > > single-node in the single-node, there is no need to config **cluster.initial\_master\_nodes** , you can remove cluster.initial\_master\_nodes and try again. ---
**Author:** ![Randomize](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Randomize](https://discuss.elastic.co/u/Randomize)\ **Post date:** [January 13, 2023, 6:47am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/4 "2023-01-13T06:47:18Z")
Yes, its single node **cluster.initial\_master\_nodes** removed. Does not helped. Still activating in systemctl status and i see warning in log ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 13, 2023, 6:55am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/5 "2023-01-13T06:55:34Z")
This message means that Elasticsearch definitely sees `cluster.initial_master_nodes` in its settings, and the only way to fix the warning is to remove the setting. Are you sure you're editing the right config file? Or maybe you're passing the setting in on the command line instead? ---
**Author:** ![Randomize](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Randomize](https://discuss.elastic.co/u/Randomize)\ **Post date:** [January 13, 2023, 7:11am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/6 "2023-01-13T07:11:13Z")
I edit /etc/elasticsearch/elasticsearch.yml The line with `cluster.initial_master_nodes` commented out in this file. I tried just remove this line. Its not helped. What does it means: "this node is locked into cluster UUID" ? How unlock node into cluster? ---
**Author:** ![Randomize](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Randomize](https://discuss.elastic.co/u/Randomize)\ **Post date:** [January 16, 2023, 8:28am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/7 "2023-01-16T08:28:49Z")
David, could you please explain what does it means: "this node is locked into cluster UUID" and how unlock node into cluster? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 16, 2023, 8:42am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/8 "2023-01-16T08:42:41Z")
Nodes can only join one cluster - after it's joined a cluster, it cannot join a different one. It is "locked in" to that specific cluster. There is no way to unlock it, apart from just deleting the contents of its data path (which wipes all the data it contains). ---
**Author:** ![Randomize](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Randomize](https://discuss.elastic.co/u/Randomize)\ **Post date:** [January 16, 2023, 9:49am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/9 "2023-01-16T09:49:39Z")
Thank you for answer, David. Is it possible to create new node in same server and transfer there data from broken node to the new one? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 16, 2023, 10:01am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/10 "2023-01-16T10:01:15Z")
The log message you quote does not mean the node is broken. ---
**Author:** ![Randomize](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Randomize](https://discuss.elastic.co/u/Randomize)\ **Post date:** [January 16, 2023, 10:07am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/11 "2023-01-16T10:07:59Z")
> [@DavidTurner](#): > > There is no way to unlock it Is any way to fix this warning without losing data? The line with `cluster.initial_master_nodes` commented out in config file. Its not helped. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 16, 2023, 10:25am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/12 "2023-01-16T10:25:02Z")
I'm not sure what to suggest beyond my previous messages: > [@This node is locked](https://discuss.elastic.co/t/this-node-is-locked/323040/5): > > This message means that Elasticsearch definitely sees cluster.initial\_master\_nodes in its settings, and the only way to fix the warning is to remove the setting. Are you sure you're editing the right config file? Or maybe you're passing the setting in on the command line instead? and > [@This node is locked](https://discuss.elastic.co/t/this-node-is-locked/323040/10): > > The log message you quote does not mean the node is broken. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 13, 2023, 10:25am UTC](https://discuss.elastic.co/t/this-node-is-locked/323040/13 "2023-02-13T10:25:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.