# Persistent high JVM usage issue (all methods tried already)
**URL:** https://discuss.elastic.co/t/persistent-high-jvm-usage-issue-all-methods-tried-already/83983
**Category:** Elasticsearch
**Created:** [April 28, 2017, 9:00am UTC](https://discuss.elastic.co/t/persistent-high-jvm-usage-issue-all-methods-tried-already/83983 "2017-04-28T09:00:09Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@macymin](https://discuss.elastic.co/u/macymin)
#### Post date: [April 28, 2017, 9:00am UTC](https://discuss.elastic.co/t/persistent-high-jvm-usage-issue-all-methods-tried-already/83983/1 "2017-04-28T09:00:09Z")
hi All,
we have a cluster consists of 15 data nodes.
we keep having high JVM heap usage (99% max) and result in elasticseach crash.
everytime when we have this issue, we have to restart the whole cluster and after awhile (few days) it crash again.
we are using elasticsearch 2.4.1 and below are the configurations we used for data node:
elaticsearch config file:
**ES\_HEAP\_SIZE=31g**
**bootstrap.memory\_lock: true**
/etc/security/limits.conf:
**elasticsearch soft nofile 65536**
**elasticsearch hard nofile 196608**
**elasticsearch soft memlock unlimited**
**elasticsearch hard memlock unlimited**
/etc/sysctl.conf:
**vm.swappiness = 1**
what can we do to resolve this issue???? please help!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 26, 2017, 9:11am UTC](https://discuss.elastic.co/t/persistent-high-jvm-usage-issue-all-methods-tried-already/83983/2 "2017-05-26T09:11:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.