# Possible values for ‘discovery-type’ (re-opening)

**URL:** <https://discuss.elastic.co/t/possible-values-for-discovery-type-re-opening/238837>\
**Category:** Elasticsearch\
**Created:** [June 26, 2020, 10:36am UTC](https://discuss.elastic.co/t/possible-values-for-discovery-type-re-opening/238837 "2020-06-26T10:36:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![formiaczek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/formiaczek/32/67778_2.png) [@formiaczek](https://discuss.elastic.co/u/formiaczek)\
**Post date:** [June 26, 2020, 10:36am UTC](https://discuss.elastic.co/t/possible-values-for-discovery-type-re-opening/238837/1 "2020-06-26T10:36:14Z")

</div>

> [@Possible values for 'discovery-type'](https://discuss.elastic.co/t/possible-values-for-discovery-type/234532):
>
> I'm looking through the docs and I can't find it. What are possible values for 'discovery\_type' config property? Why I can only find references to single-node value?

no longer allows to add replies.. (nor to re-open it) .

I'm not satisfied with this setting, given @DavidTurner's answer:

> `single-node` is the only permitted value for `discovery.type` . The only other option is not to set it at all.

How would one 'script' it (or make an 'env variable' value) in elasticsearch.yml?

Would be good to be able to run a node in two modes: if this setting has only one possible value it should not be called 'type', but rather

`discovery.single_node_mode: true`

(and default it to false)

QUestion: if in elasticsearch.yml I use:

`discovery.type: ${ES_DISCOVERY_TYPE}`

and then I run it with either:  
ES\_DISCOVERY\_TYPE set to 'single-node', or not set at all =\> will it be okay (and valid) to run ith with empty value?

And you should consider deprecating this setting and adding such a flag instead really..

THanks,  
Lukasz.

@tmporary

---

<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 26, 2020, 1:03pm UTC](https://discuss.elastic.co/t/possible-values-for-discovery-type-re-opening/238837/2 "2020-06-26T13:03:41Z")

</div>

I wouldn't recommend using this setting at all. It's only there to bypass some [safety checks](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html) for simple test environments. If you're scripting your deployment you shouldn't need to do that.

> [@formiaczek](#):
>
> And you should consider deprecating this setting and adding such a flag instead really..

We're actually [considering removing it entirely](https://github.com/elastic/elasticsearch/issues/58393).

---

<div class="post-metadata">

**Author:** ![formiaczek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/formiaczek/32/67778_2.png) [@formiaczek](https://discuss.elastic.co/u/formiaczek)\
**Post date:** [June 26, 2020, 1:11pm UTC](https://discuss.elastic.co/t/possible-values-for-discovery-type-re-opening/238837/3 "2020-06-26T13:11:30Z")

</div>

Great, I actually just verified and wanted to mention it - that it does not seem to be needed any more!  
Thanks for reply!

---

<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:** [July 24, 2020, 1:15pm UTC](https://discuss.elastic.co/t/possible-values-for-discovery-type-re-opening/238837/4 "2020-07-24T13:15:56Z")

</div>

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