# I'm Getting Master Not Discovered Exception On Remote Server

**URL:** https://discuss.elastic.co/t/im-getting-master-not-discovered-exception-on-remote-server/188508
**Category:** Elasticsearch
**Created:** [July 2, 2019, 12:15pm UTC](https://discuss.elastic.co/t/im-getting-master-not-discovered-exception-on-remote-server/188508 "2019-07-02T12:15:18Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Jurgen\_Debedts](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jurgen_debedts/32/49335_2.png) [@Jurgen\_Debedts](https://discuss.elastic.co/u/Jurgen_Debedts)
#### Post date: [July 8, 2019, 6:32pm UTC](https://discuss.elastic.co/t/im-getting-master-not-discovered-exception-on-remote-server/188508/6 "2019-07-08T18:32:34Z")

</div>

There is actually some info in here as well that seems to correspond to your issue.

> [@2 node cluster on Elasticsearch 7.0.1](https://discuss.elastic.co/t/2-node-cluster-on-elasticsearch-7-0-1/189127):
>
> Hi We had configured a 2 node cluster on Elasticsearch 6.x with both nodes configured as master eligible and the minimum number of master nodes configured to 1. We found this worked for our requirements particularly where if either node was temporarily removed from the cluster (if it is being upgraded or when simulating a node failure) the other node was automatically elected as the master. Following an upgrade to Elasticsearch 7.0.1 we find that this is no longer the case, when the currently…

I would seriously consider not to configure your installation as a cluster is you are going to have only 1 single node.

Regards,

Jurgen

---

_[View the full topic](https://discuss.elastic.co/t/im-getting-master-not-discovered-exception-on-remote-server/188508)._