# Run Elasticsearch-5.4.0 in low memory environment

**URL:** <https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032>\
**Category:** Elasticsearch\
**Created:** [May 17, 2017, 2:22am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032 "2017-05-17T02:22:24Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [May 17, 2017, 2:22am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/1 "2017-05-17T02:22:25Z")

</div>

Can we not run elasticsearch-5.4.0 on a system with lower memory cofig. Somewhere I came across that 32-64GB of system memory would be required.

I am trying to run it on a Fedora box with 6GB of System memory and it crashes as soon as elasticsearch starts running. Getting OOM(verified using dmegs).

---

<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:** [May 17, 2017, 2:22am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/2 "2017-05-17T02:22:56Z")

</div>

Can you post the log?

---

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [May 17, 2017, 2:31am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/3 "2017-05-17T02:31:03Z")

</div>

This is the message I get in virtualBox prompt - Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM.

Earlier I was getting a "Killed" message in the startup logs of elasticsearch. but as of now the system halts and hence I am not able to get these logs.

---

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [May 17, 2017, 4:01am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/4 "2017-05-17T04:01:37Z")

</div>

Got around this one. This was probably due to uneven memory allocation to the VM installed locally.

However the elasticsearch process is being killed on another machine with ~2 GB of system memory.  
Below is the invocation log -

> ```
> [admin@ELKTEST elasticsearch-5.4.0]$ ./bin/elasticsearch
> [2017-05-17T05:52:41,135][INFO][o.e.n.Node] [] initializing ...
> [2017-05-17T05:52:41,618][INFO][o.e.e.NodeEnvironment] [uzJHHwZ] using [1] data paths, mounts [[/home (/dev/mapper/rootvg-home_lv)]], net usable_space [2.3gb], net total_space [2.9gb], spins? [possibly], types [ext4]
> [2017-05-17T05:52:41,619][INFO][o.e.e.NodeEnvironment] [uzJHHwZ] heap size [1.9gb], compressed ordinary object pointers [true]
> [2017-05-17T05:52:41,623][INFO][o.e.n.Node] node name [uzJHHwZ] derived from node ID [uzJHHwZiSkyqddIMA9qKnw]; set [node.name] to override
> [2017-05-17T05:52:41,624][INFO][o.e.n.Node] version[5.4.0], pid[6010], build[780f8c4/2017-04-28T17:43:27.229Z], OS[Linux/3.10.0-327.22.2.el7.x86_64/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_101/25.101-b13]
> [2017-05-17T05:52:47,046][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [aggs-matrix-stats]
> [2017-05-17T05:52:47,047][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [ingest-common]
> [2017-05-17T05:52:47,047][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [lang-expression]
> [2017-05-17T05:52:47,047][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [lang-groovy]
> [2017-05-17T05:52:47,047][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [lang-mustache]
> [2017-05-17T05:52:47,047][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [lang-painless]
> [2017-05-17T05:52:47,048][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [percolator]
> [2017-05-17T05:52:47,048][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [reindex]
> [2017-05-17T05:52:47,048][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [transport-netty3]
> [2017-05-17T05:52:47,048][INFO][o.e.p.PluginsService] [uzJHHwZ] loaded module [transport-netty4]
> [2017-05-17T05:52:47,049][INFO][o.e.p.PluginsService] [uzJHHwZ] no plugins loaded
> [2017-05-17T05:52:54,932][INFO][o.e.d.DiscoveryModule] [uzJHHwZ] using discovery type [zen]
> [2017-05-17T05:53:00,960][INFO][o.e.n.Node] initialized
> [2017-05-17T05:53:00,963][INFO][o.e.n.Node] [uzJHHwZ] starting ...
> [2017-05-17T05:53:02,538][INFO][o.e.t.TransportService] [uzJHHwZ] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}
> [2017-05-17T05:53:05,514][INFO][o.e.m.j.JvmGcMonitorService] [uzJHHwZ] [gc][4] overhead, spent [301ms] collecting in the last [1s]
> [2017-05-17T05:53:07,437][INFO][o.e.c.s.ClusterService] [uzJHHwZ] new_master {uzJHHwZ}{uzJHHwZiSkyqddIMA9qKnw}{MkUr8HHoQ7mRC9fdq58Ktw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
> [2017-05-17T05:53:08,624][INFO][o.e.h.n.Netty4HttpServerTransport] [uzJHHwZ] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}
> [2017-05-17T05:53:09,171][INFO][o.e.n.Node] [uzJHHwZ] started
> [2017-05-17T05:53:09,703][INFO][o.e.g.GatewayService] [uzJHHwZ] recovered [0] indices into cluster_state
> Killed
> 
> ```

Here is the trailing messages from **dmesg** -

> [1124233.764011] [5997] 249 5997 36396 1 70 352 0 sshd  
> [1124233.765125] [5998] 249 5998 13175 0 29 137 0 sftp-server  
> [1124233.766194] [6010] 249 6010 1062691 386225 1173 182024 0 java  
> [1124233.767205] [6077] 0 6077 15852 95 31 0 0 sshd  
> [1124233.768178] Out of memory: Kill process 6010 (java) score 776 or sacrifice child  
> [1124233.769158] Killed process 6010 (java) total-vm:4250764kB, anon-rss:1544900kB, file-rss:0kB

---

<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:** [May 17, 2017, 6:28am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/5 "2017-05-17T06:28:15Z")

</div>

So it's the OS OOMkiller, you may want to look how to change that based on your OS documentation.

---

<div class="post-metadata">

**Author:** ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)\
**Post date:** [May 17, 2017, 6:57am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/6 "2017-05-17T06:57:10Z")

</div>

what is your JVM settings?

---

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [May 17, 2017, 9:17am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/7 "2017-05-17T09:17:17Z")

</div>

I had done no extra JVM configurations.

However I tried running elasticsearch with [extra configs](https://www.elastic.co/guide/en/elasticsearch/reference/master/heap-size.html) by invoking -  
`ES_JAVA_OPTS="-Xms1g -Xmx1g" ./bin/elasticsearch`

It is running fine on the same machine now though I have switched to 5.3.0. Will next try 5.4.0 again.

Thanku for the lead @warkolm @Vitaly_il

---

<div class="post-metadata">

**Author:** ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)\
**Post date:** [May 17, 2017, 10:02am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/8 "2017-05-17T10:02:09Z")

</div>

Are there other RAM-intensive processes on this Linux box?

---

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [May 17, 2017, 10:03am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/9 "2017-05-17T10:03:46Z")

</div>

No. Just a test machine I am using.

---

<div class="post-metadata">

**Author:** ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)\
**Post date:** [May 17, 2017, 10:08am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/10 "2017-05-17T10:08:28Z")

</div>

Weird. What is  
free -m  
output?

---

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [May 17, 2017, 10:11am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/11 "2017-05-17T10:11:53Z")

</div>

When I was running into the issue, for both mem and swap it was a single digit or 0.

---

<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:** [June 14, 2017, 10:12am UTC](https://discuss.elastic.co/t/run-elasticsearch-5-4-0-in-low-memory-environment/86032/12 "2017-06-14T10:12:19Z")

</div>

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