# Elasticsearch 5.1 on AWS ubuntu image

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745>\
**Category:** Elasticsearch\
**Created:** [December 22, 2016, 7:36am UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745 "2016-12-22T07:36:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarti/32/14064_2.png) [@sarti](https://discuss.elastic.co/u/sarti)\
**Post date:** [December 22, 2016, 7:36am UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/1 "2016-12-22T07:36:36Z")

</div>

Elasticsearch DB has stoped working after it was upgraded to version 5.  
I am working on a AWS ubuntu image environment. and while I was running on version 2.3 it all was perfect . When I tried to upgrade to version 5 it suddenly could not run any longer because of java memory issues.

Has any one shared the same problem? what was the solution?

---

<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:** [December 22, 2016, 8:41am UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/2 "2016-12-22T08:41:16Z")

</div>

What is the problem?  
I mean: did you look at your logs?

---

<div class="post-metadata">

**Author:** ![sarti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarti/32/14064_2.png) [@sarti](https://discuss.elastic.co/u/sarti)\
**Post date:** [December 22, 2016, 10:37am UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/3 "2016-12-22T10:37:16Z")

</div>

here is the error:

> OpenJDK 64-Bit Server VM warning: INFO: os::commit\_memory(0x0000000085330000, 2060255232, 0) failed; error='Cannot allocate memory' (errno=12)

> There is insufficient memory for the Java Runtime Environment to continue.  
> Native memory allocation (mmap) failed to map 2060255232 bytes for committing reserved memory.

---

<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:** [December 22, 2016, 11:15am UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/4 "2016-12-22T11:15:00Z")

</div>

So you don't have 2gb of free RAM on your machine apparently?

---

<div class="post-metadata">

**Author:** ![sarti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarti/32/14064_2.png) [@sarti](https://discuss.elastic.co/u/sarti)\
**Post date:** [December 23, 2016, 6:52pm UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/5 "2016-12-23T18:52:49Z")

</div>

I see what you're saying.

However, how come it worked fine before the upgrade? was there new system requirements for the new version compare to previous ones?

---

<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:** [December 23, 2016, 7:28pm UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/6 "2016-12-23T19:28:38Z")

</div>

Yes. I think the default values are now 2gb

---

<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:** [January 20, 2017, 7:28pm UTC](https://discuss.elastic.co/t/elasticsearch-5-1-on-aws-ubuntu-image/69745/7 "2017-01-20T19:28:51Z")

</div>

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