# Timed out while waiting for initial discovery state - timeout: 30s **URL:** \ **Category:** Elasticsearch\ **Created:** [August 26, 2018, 3:02am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055 "2018-08-26T03:02:30Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 26, 2018, 3:02am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/1 "2018-08-26T03:02:30Z")
I'm using Elastic Stack 6.4.0 (did rolling upgrade from 6.3.2 recently) and after stop of entire elasticsearch cluster (master, data, coordinate and ingest nodes), I'm no longer able to start it; I'm getting following messages in logs: > timed out while waiting for initial discovery state - timeout: 30s and also: > org.elasticsearch.discovery.MasterNotDiscoveredException: null I use `Zen Discovery` and `publish_host` seems to be correct. Please advise. ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 26, 2018, 9:24pm UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/2 "2018-08-26T21:24:29Z")
after downgrading Elastic Stack to 6.3.2 (and later rolling upgrade to 6.4.0) everything works as it expected, however starting with 6.4.0 cluster Elastic Stack, causing nodes not see each other... ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 27, 2018, 1:09am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/3 "2018-08-27T01:09:30Z")
Can you share your full config and the logs? ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 27, 2018, 4:09am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/4 "2018-08-27T04:09:30Z")
My elasticsearch cluster consist of: 5 master eligible nodes 5 data nodes 2 injest nodes and few coordinate only nodes they all share following configuration: ``` # cat cluster.env cluster.name=X # cat discovery.zen.env discovery.zen.minimum_master_nodes=3 discovery.zen.ping.unicast.hosts=esm1,esm2,esm3,esm4,esm5 # ``` esm = master nodes unfortunately, I blew everything away to go to plan "b", which I commented earlier... ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 27, 2018, 4:10am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/5 "2018-08-27T04:10:07Z")
Are they dedicated master nodes? ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 27, 2018, 4:10am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/6 "2018-08-27T04:10:46Z")
yes, and they have 12G HEAP memory ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 27, 2018, 4:12am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/7 "2018-08-27T04:12:22Z")
You really only need 3, 5 is a bit of overkill. Without full logs it's a little hard to speculate as to why this is happening. ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 27, 2018, 4:14am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/8 "2018-08-27T04:14:05Z")
5 allows me to do rolling upgrades w/ minimal downtime ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 27, 2018, 4:15am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/9 "2018-08-27T04:15:48Z")
You can do the same thing with 3. Having dedicated masters is great, but having more than 3 is diminishing returns. ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 27, 2018, 4:19am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/10 "2018-08-27T04:19:20Z")
I have following line: discovery.zen.minimum\_master\_nodes=3 if I only have 3 nodes, and I restart one of them, cluster still green? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 27, 2018, 4:20am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/11 "2018-08-27T04:20:46Z")
You just reduce that to 2, which is still a majority of 3. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 24, 2018, 4:21am UTC](https://discuss.elastic.co/t/timed-out-while-waiting-for-initial-discovery-state-timeout-30s/146055/12 "2018-09-24T04:21:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.