# Elasticsearch cluster down: no known master node, scheduling a retry
**URL:** https://discuss.elastic.co/t/elasticsearch-cluster-down-no-known-master-node-scheduling-a-retry/93216
**Category:** Elasticsearch
**Created:** [July 14, 2017, 4:05pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-down-no-known-master-node-scheduling-a-retry/93216 "2017-07-14T16:05:33Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@jeffsaremi](https://discuss.elastic.co/u/jeffsaremi)
#### Post date: [July 14, 2017, 4:05pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-down-no-known-master-node-scheduling-a-retry/93216/1 "2017-07-14T16:05:33Z")
UPDATE 7/17/2017
I restarted it and everything is ok now.
I guess based on my settings i needed a minimum of 3 nodes to be available for a master to to be elected and we didn't have 3 nodes at the time.
This was for Elasticsearch 5.4
* * *
We have a 5 node cluster which was running fine until last week. This week, even though processes seem to be running they are either not logging or logging errors like:
[o.e.a.a.i.c.TransportCreateIndexAction] [CO4SCH010031328] no known master node, scheduling a retry
My understanding is ES is by default in HA mode and I don't need to set anything specifically for that to happen other than these important settings:
[cluster.name](http://cluster.name): mycluster
network.bind\_host: 0.0.0.0
http.port: 9200
discovery.zen.ping.unicast.hosts: ["server1", "server2", "server3", "server4", "server5"]
discovery.zen.minimum\_master\_nodes: 3
thanks
Jeff
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 17, 2017, 5:07am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-down-no-known-master-node-scheduling-a-retry/93216/2 "2017-07-17T05:07:40Z")
What version are you on?
What does `_cat/nodes` show?
---
### Author:  [@jeffsaremi](https://discuss.elastic.co/u/jeffsaremi)
#### Post date: [July 17, 2017, 5:02pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-down-no-known-master-node-scheduling-a-retry/93216/3 "2017-07-17T17:02:33Z")
I restarted it and everything is ok now.
I guess based on my settings i needed a minimum of 3 nodes to be available for a master to to be elected and we didn't have 3 nodes at the time.
This was for Elasticsearch 5.4
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 14, 2017, 5:02pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-down-no-known-master-node-scheduling-a-retry/93216/4 "2017-08-14T17:02:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.