# How to avoid warning when starting with discovery.type set to single node

**URL:** <https://discuss.elastic.co/t/how-to-avoid-warning-when-starting-with-discovery-type-set-to-single-node/334087>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [May 23, 2023, 7:27am UTC](https://discuss.elastic.co/t/how-to-avoid-warning-when-starting-with-discovery-type-set-to-single-node/334087 "2023-05-23T07:27:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![PeterNagel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peternagel/32/122304_2.png) [@PeterNagel](https://discuss.elastic.co/u/PeterNagel)\
**Post date:** [June 15, 2023, 1:38pm UTC](https://discuss.elastic.co/t/how-to-avoid-warning-when-starting-with-discovery-type-set-to-single-node/334087/4 "2023-06-15T13:38:49Z")

</div>

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/how-to-avoid-warning-when-starting-with-discovery-type-set-to-single-node/334087)._