# Java process been swapped with mlockall True

**URL:** <https://discuss.elastic.co/t/java-process-been-swapped-with-mlockall-true/102127>\
**Category:** Elasticsearch\
**Created:** [September 28, 2017, 2:12pm UTC](https://discuss.elastic.co/t/java-process-been-swapped-with-mlockall-true/102127 "2017-09-28T14:12:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DravenJohnson](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@DravenJohnson](https://discuss.elastic.co/u/DravenJohnson)\
**Post date:** [September 28, 2017, 2:12pm UTC](https://discuss.elastic.co/t/java-process-been-swapped-with-mlockall-true/102127/1 "2017-09-28T14:12:49Z")

</div>

Our cluster is running with 0 Swap set and mlockall on, but we ran into a lot OOM-killed situation that system killed elasticsearch processes due to OOM.

So we are thinking and testing the [swappiness option](https://www.elastic.co/guide/en/elasticsearch/reference/5.4/setup-configuration-memory.html#swappiness)

After few days test, seem like Java process that run elasticsearch still been swapped when node is overloaded. Why mlockall did prevent that happen?

Also, OOM-kill only start happening recently after we upgrade our cluster to 5.4.x. Is there anything that new introduced in 5.x version?

---

<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:** [October 26, 2017, 2:12pm UTC](https://discuss.elastic.co/t/java-process-been-swapped-with-mlockall-true/102127/2 "2017-10-26T14:12:57Z")

</div>

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