# Elasticsearch & Kibana JVM Management
**URL:** https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339
**Category:** Elasticsearch
**Created:** [November 17, 2016, 7:28am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339 "2016-11-17T07:28:30Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [November 17, 2016, 7:28am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/1 "2016-11-17T07:28:30Z")
Hi everyone,
I have a doubt about _JVM usage_ with **Elasticsarch** & **Kibana**. For example, I have an **Elasticsearch 1.7.5** and **Kibana 3**. In a normal conditions **Elasticsearch** has _30%_ heap usage, when I use **Kibana** and I try to obtain information, jvm heap usage increase to _60%_ or _70%_.
When I stop using **Kibana** , this JVM heap usage remains, so, how long time **Elasticsearch**
needs to free this JVM? Is there any way to accelerate it?
Another question, it would be advisable to use **Elasticsearch 2.x** or **5.x** to improve it?
Thanks in advance 🙂,
Regards
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [November 17, 2016, 7:43am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/2 "2016-11-17T07:43:53Z")
Is there any problem that the JVM usage is still at 60% or 70%?
Unless you are seeing errors or warnings about the garbage collector, I'd not really care about this.
---
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [November 17, 2016, 8:05am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/3 "2016-11-17T08:05:21Z")
Hi David,
First of all, thanks for your answer. Regarding to my doubt,the problem is that if I come back to use **Kibana 3** (for example, another **Dashboards** or the same), JVM usage increases until _90%_ or _100%_. So , the errors appears like (example of Internet):
> [2015-07-01 06:43:19,525][INFO][monitor.jvm] [my\_node] [gc][old][205450][116]duration [5.7s], collections [1]/[6.3s], total [5.7s]/[1m],memory [22.3gb]-\>[4.9gb]/[30.9gb]
If I stop using **Kibana** , why the JVM heap usage remains?
Thanks in advance,
Regards
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [November 17, 2016, 8:23am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/4 "2016-11-17T08:23:41Z")
You are running low on memory for sure. So answering now to this question:
> it would be advisable to use Elasticsearch 2.x or 5.x to improve it?
Yes. Definitely. Before 2.x you were using I guess field data a lot. It has been "replaced" by doc\_values.
Also, lot of improvements since Kibana3 when it comes to querying ES.
I'd go to that way.
---
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [November 17, 2016, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/5 "2016-11-17T08:32:05Z")
Thank you very much for your advise 🙂.
Regards
---
### Author:  [@Miguel1](https://discuss.elastic.co/u/Miguel1)
#### Post date: [November 18, 2016, 2:34pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/6 "2016-11-18T14:34:03Z")
Hello! I 'm using 2.4 version of Elasticsearch and I'm having the same issues. Even if I close all the Indexes the JVM doesn't decrease. Is there any place where I can find docs about the internal processes of Elasticsearch? Is there any way to reduce of memory usage?
I've tried to clean, shrink and forcemerge to: get the cache cleaned and reduce the shards/indexes but nothing worked for me.
Thank you in advance,
Miguel
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 16, 2016, 2:34pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-jvm-management/66339/7 "2016-12-16T14:34:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.