# Master not discovered exception for two node cluster

**URL:** <https://discuss.elastic.co/t/master-not-discovered-exception-for-two-node-cluster/243452>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [August 2, 2020, 10:11am UTC](https://discuss.elastic.co/t/master-not-discovered-exception-for-two-node-cluster/243452 "2020-08-02T10:11:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [August 2, 2020, 11:12am UTC](https://discuss.elastic.co/t/master-not-discovered-exception-for-two-node-cluster/243452/3 "2020-08-02T11:12:00Z")

</div>

From [the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-small-clusters.html#high-availability-cluster-design-two-nodes):

> Because it’s not resilient to failures, we do not recommend deploying a two-node cluster in production.

Those docs also answer your question about three node clusters.

---

_[View the full topic](https://discuss.elastic.co/t/master-not-discovered-exception-for-two-node-cluster/243452)._