# Elastic can not start because of memory issue

**URL:** <https://discuss.elastic.co/t/elastic-can-not-start-because-of-memory-issue/282711>\
**Category:** Elasticsearch\
**Created:** [August 27, 2021, 10:40pm UTC](https://discuss.elastic.co/t/elastic-can-not-start-because-of-memory-issue/282711 "2021-08-27T22:40:41Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [August 29, 2021, 6:02pm UTC](https://discuss.elastic.co/t/elastic-can-not-start-because-of-memory-issue/282711/13 "2021-08-29T18:02:06Z")

</div>

Understood I am just relating best practices and why you are having issues.

Elasticsearch can run like this, **BUT** Elasticsearch will not run / will not run well if it can not claim the RAM it needs. So if 1gb of RAM works then fine. Also you can always start elasticsearch first let it claim its RAM then let the other processes "fight" of the remaining RAM.

So in this case you need to manually set the elasticsearch RAM as you just did... 1GB is pretty small... it may or may not work well depending on how many shards, ingest per sec, queries etc. you can always bump it up.

If it is not running well bump it up to 2 or 4 GB and start it first and so on.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-can-not-start-because-of-memory-issue/282711)._
