# Getting org.elasticsearch.discovery.MasterNotDiscoveredException, while I use only one node **URL:** \ **Category:** Elasticsearch\ **Created:** [September 15, 2020, 11:04am UTC](https://discuss.elastic.co/t/getting-org-elasticsearch-discovery-masternotdiscoveredexception-while-i-use-only-one-node/248662 "2020-09-15T11:04:45Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![111320](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/111320/32/66612_2.png) [@111320](https://discuss.elastic.co/u/111320)\ **Post date:** [September 17, 2020, 6:19am UTC](https://discuss.elastic.co/t/getting-org-elasticsearch-discovery-masternotdiscoveredexception-while-i-use-only-one-node/248662/4 "2020-09-17T06:19:26Z")
Thanks Mark. I will describe what happen to my system maybe it will help others. I has a system with 5 nodes. In some point I was asked to use only one node since this system wasn't in real use. So I moved all indices to one node and use it. All was good in the beginning but when I tried to save some visualizations and search I get errors. After investigation I found this discussion [Getting "master not discovered or elected yet" causing cluster not up in version 7.1.0](https://discuss.elastic.co/t/getting-master-not-discovered-or-elected-yet-causing-cluster-not-up-in-version-7-1-0/182489/20) and I saw David's answer about the problem that can be if some nodes were dropped from the system. I deleted all my data from `path.data` but I still had the same issue. After your answer I read [here](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/modules-discovery-bootstrap-cluster.html) that in the first time we bootstrap a cluster we must define `cluster.initial_master_nodes` so I did it and now it looks good. Thanks --- _[View the full topic](https://discuss.elastic.co/t/getting-org-elasticsearch-discovery-masternotdiscoveredexception-while-i-use-only-one-node/248662)._