# Elastic search is not starting

**URL:** <https://discuss.elastic.co/t/elastic-search-is-not-starting/124520>\
**Category:** Elasticsearch\
**Created:** [March 19, 2018, 9:34am UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520 "2018-03-19T09:34:12Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 19, 2018, 11:43am UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520/21 "2018-03-19T11:43:58Z")

</div>

What kind of host are you running this node on? How is the node configured?

---

<div class="post-metadata">

**Author:** ![prahlad574](https://avatars.discourse-cdn.com/v4/letter/p/958977/32.png) [@prahlad574](https://discuss.elastic.co/u/prahlad574)\
**Post date:** [March 19, 2018, 5:58pm UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520/22 "2018-03-19T17:58:45Z")

</div>

Default configuration Ubuntu server 14

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 19, 2018, 5:59pm UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520/23 "2018-03-19T17:59:40Z")

</div>

Base metal server, VM, cloud instance? How many cores? How much RAM?

---

<div class="post-metadata">

**Author:** ![prahlad574](https://avatars.discourse-cdn.com/v4/letter/p/958977/32.png) [@prahlad574](https://discuss.elastic.co/u/prahlad574)\
**Post date:** [March 20, 2018, 12:06pm UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520/24 "2018-03-20T12:06:35Z")

</div>

t2.micro (Variable ECUs, 1 vCPUs, 2.5 GHz, Intel Xeon Family, 1 GiB memory, EBS only)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 20, 2018, 12:15pm UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520/25 "2018-03-20T12:15:49Z")

</div>

That is not a very suitable instance type to run Elasticsearch on in my opinion. It has very little RAM, and though you may be able to get away with using a 512MB heap, it is less than is recommended for production. Another, and possibly more severe, issue with this type of instance is that it has very little CPU resources available and that this is not constantly available.

I would assume you have much more CPU resources available when you are running it in VirtualBox, which might explain the difference in performance and stability.

---

<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 17, 2018, 12:16pm UTC](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520/26 "2018-04-17T12:16:10Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/elastic-search-is-not-starting/124520.md?page=1)