# Can't get rid of warning "this node is locked into cluster UUID but \[cluster.initial\_master\_nodes\] is set to \[Z56EEW81\]; remove this setting to avoid possible data loss caused by subsequent cluster bootstrap attempts"

**URL:** <https://discuss.elastic.co/t/cant-get-rid-of-warning-this-node-is-locked-into-cluster-uuid-but-cluster-initial-master-nodes-is-set-to-z56eew81-remove-this-setting-to-avoid-possible-data-loss-caused-by-subsequent-cluster-bootstrap-attempts/335889>\
**Category:** Elasticsearch\
**Created:** [June 13, 2023, 3:38pm UTC](https://discuss.elastic.co/t/cant-get-rid-of-warning-this-node-is-locked-into-cluster-uuid-but-cluster-initial-master-nodes-is-set-to-z56eew81-remove-this-setting-to-avoid-possible-data-loss-caused-by-subsequent-cluster-bootstrap-attempts/335889 "2023-06-13T15:38:53Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**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:** [June 15, 2023, 1:57pm UTC](https://discuss.elastic.co/t/cant-get-rid-of-warning-this-node-is-locked-into-cluster-uuid-but-cluster-initial-master-nodes-is-set-to-z56eew81-remove-this-setting-to-avoid-possible-data-loss-caused-by-subsequent-cluster-bootstrap-attempts/335889/5 "2023-06-15T13:57:15Z")

</div>

Ah wait, in another similar thread a user points out that this warning appears to be emitted incorrectly in the case of `discovery.type: single-node`:

> [@How to avoid warning when starting with discovery.type set to single node](https://discuss.elastic.co/t/how-to-avoid-warning-when-starting-with-discovery-type-set-to-single-node/334087/4):
>
> I believe there is a bug in de code that logs the warning ([elasticsearch/server/src/main/java/org/elasticsearch/cluster/coordination/ClusterBootstrapService.java at main · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/cluster/coordination/ClusterBootstrapService.java)). The assumption is made that bootstrapRequirements is filled with the cluster.initial\_master\_nodes setting, but in fact it is filled with the node.name setting in case of single node discovery

---

_[View the full topic](https://discuss.elastic.co/t/cant-get-rid-of-warning-this-node-is-locked-into-cluster-uuid-but-cluster-initial-master-nodes-is-set-to-z56eew81-remove-this-setting-to-avoid-possible-data-loss-caused-by-subsequent-cluster-bootstrap-attempts/335889)._