# Upgraded data nodes and now seeing volatile JVM memory pressure

**URL:** <https://discuss.elastic.co/t/upgraded-data-nodes-and-now-seeing-volatile-jvm-memory-pressure/138791>\
**Category:** Elasticsearch\
**Created:** [July 5, 2018, 7:54pm UTC](https://discuss.elastic.co/t/upgraded-data-nodes-and-now-seeing-volatile-jvm-memory-pressure/138791 "2018-07-05T19:54:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nodesocket](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nodesocket/32/27023_2.png) [@nodesocket](https://discuss.elastic.co/u/nodesocket)\
**Post date:** [July 5, 2018, 7:54pm UTC](https://discuss.elastic.co/t/upgraded-data-nodes-and-now-seeing-volatile-jvm-memory-pressure/138791/1 "2018-07-05T19:54:59Z")

</div>

Hello. We have a two data node and three dedicated master node cluster on AWS Elasticsearch service.

Currently have about 3 billion documents (1.1TB of data) and data nodes were previously running 2 cpus and 15GB of memory each. We upgraded the data nodes to 4 cpus and 30 GB of memory each after noticing CPU load was nearly pegged at 98% constantly.

After the upgrade, the JVM memory pressure is MUCH MORE volatile with huge peaks and valleys. See the graph:

 ![57%20PM](https://us1.discourse-cdn.com/elastic/original/3X/9/d/9dfa92cb26cb53e19567c1b6e2076d75d6a090e3.png)

Is this expected? Does this indicate that the cluster still is under provisioned in terms of memory? Here is a graph of CPU usage showing the old cluster and new cluster performance:

 ![42%20PM](https://us1.discourse-cdn.com/elastic/original/3X/b/7/b7f6c13be37854654efd5c65214d94ad039e9789.png)

---

<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:** [July 6, 2018, 12:57am UTC](https://discuss.elastic.co/t/upgraded-data-nodes-and-now-seeing-volatile-jvm-memory-pressure/138791/2 "2018-07-06T00:57:25Z")

</div>

I think that looks better, because rather than seeing resources being nearly entirely and continually used, you are seeing use and then recovery.

---

<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:** [August 3, 2018, 12:57am UTC](https://discuss.elastic.co/t/upgraded-data-nodes-and-now-seeing-volatile-jvm-memory-pressure/138791/3 "2018-08-03T00:57:27Z")

</div>

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