# ES is taking significant time to start

**URL:** https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993
**Category:** Elasticsearch
**Created:** [March 21, 2018, 1:25pm UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993 "2018-03-21T13:25:31Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![dimalini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dimalini/32/22448_2.png) [@dimalini](https://discuss.elastic.co/u/dimalini)
#### Post date: [March 21, 2018, 1:25pm UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/1 "2018-03-21T13:25:31Z")

</div>

We are starting the ES process using the bat file in version 5.4

**[2018-03-21T15:40:42,295]**[INFO][o.e.n.Node] [hxa\_pUV] starting ...  
[2018-03-21T15:46:20,944][INFO][o.e.t.TransportService] [hxa\_pUV] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300}, {[::1]:9300}  
[2018-03-21T15:46:23,981][INFO][o.e.c.s.ClusterService] [hxa\_pUV] new\_master {hxa\_pUV}{hxa\_pUVDSGqXgwSipL-sxw}{Lw8gBGtAQY-9r0ojPPB9rw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)  
[2018-03-21T15:46:24,025][INFO][o.e.g.GatewayService] [hxa\_pUV] recovered [0] indices into cluster\_state  
[2018-03-21T15:49:17,086][INFO][o.e.h.n.Netty4HttpServerTransport] [hxa\_pUV] publish\_address {127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200}, {[::1]:9200}  
[**2018-03-21T15:49:17,089**][INFO][o.e.n.Node] [hxa\_pUV] started

We started seeing this in a set of machines(not all) recently. And it seems to be pretty consistent in those machines.

Any pointers on how to debug/fix this ?

Thanks, Divya

---

<div class="post-metadata">

### 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: [March 22, 2018, 5:36am UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/2 "2018-03-22T05:36:13Z")

</div>

That is pretty slow. What are the resources on the node? What JVM?

---

<div class="post-metadata">

### Author: ![dimalini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dimalini/32/22448_2.png) [@dimalini](https://discuss.elastic.co/u/dimalini)
#### Post date: [March 22, 2018, 6:12am UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/3 "2018-03-22T06:12:26Z")

</div>

The node(single) has no data. We are using 1.61 java.

Note: With the same machine configurations and Java versions its working fine for most of the people.

---

<div class="post-metadata">

### Author: ![Dvikas](https://avatars.discourse-cdn.com/v4/letter/d/a9adbd/32.png) [@Dvikas](https://discuss.elastic.co/u/Dvikas)
#### Post date: [March 22, 2018, 6:19am UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/4 "2018-03-22T06:19:53Z")

</div>

**We recommend installing Java version 1.8.0\_131 or a later version in the Java 8 release series**.  
I hope this is clearly mentioned in elk document.  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html)  
how it is possible that others instance is running.🤔

---

<div class="post-metadata">

### Author: ![dimalini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dimalini/32/22448_2.png) [@dimalini](https://discuss.elastic.co/u/dimalini)
#### Post date: [March 22, 2018, 10:52am UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/5 "2018-03-22T10:52:18Z")

</div>

Sorry about the typo: this is the exact java version we are using - "installed java version: 1.8.0.72"

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 22, 2018, 11:04am UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/6 "2018-03-22T11:04:42Z")

</div>

So upgrade the JVM at least.

---

<div class="post-metadata">

### Author: ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)
#### Post date: [March 23, 2018, 2:58am UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/7 "2018-03-23T02:58:18Z")

</div>

The six seconds from `starting ...` to `publish_address` are the problem here, the other three seconds are expected from discovery. Would you please start Elasticsearch with `-E logger.level=debug` and post all the log lines _between_ `starting ...` to `publish_address`?

---

<div class="post-metadata">

### Author: ![dimalini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dimalini/32/22448_2.png) [@dimalini](https://discuss.elastic.co/u/dimalini)
#### Post date: [March 29, 2018, 2:22pm UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/8 "2018-03-29T14:22:49Z")

</div>

The issue seems to have occurred due to some upgrade of OS. Post an another update this got fixed. Thanks for the suggestions.

Next time if we encounter the same, I'll try to share the logs as suggested.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 26, 2018, 2:28pm UTC](https://discuss.elastic.co/t/es-is-taking-significant-time-to-start/124993/9 "2018-04-26T14:28:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
