# Upgrading cluster resource still the consumptions remains same

**URL:** <https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250>\
**Category:** Elasticsearch\
**Created:** [August 22, 2019, 7:00am UTC](https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250 "2019-08-22T07:00:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hitesh\_Baldaniya1](https://avatars.discourse-cdn.com/v4/letter/h/45deac/32.png) [@Hitesh\_Baldaniya1](https://discuss.elastic.co/u/Hitesh_Baldaniya1)\
**Post date:** [August 22, 2019, 7:00am UTC](https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250/1 "2019-08-22T07:00:14Z")

</div>

Hi Team,

We were working on the cluster of 2 data nodes(8 GB of each) + 1 master node(8GB)(I/O Optimized template), with data size of 7.7GB (16GB with replication).  
We have only 1 index with 5 shards. Cluster used to always on 75-85% JVM pressure.

Later, we decided to upgrade the cluster and changed the data node RAM to 16 GB for each. Data size, indexes and shards still remains the same.

Still, the cluster shows JVM heap pressure of 60 to 70%. Is it normal or expected behaviour?

Thanks,

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 22, 2019, 7:03am UTC](https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250/2 "2019-08-22T07:03:16Z")

</div>

The JVM starts GC at 75% so 60% to 70% is generally not a problem as long as it drops when it reaches 75%.

---

<div class="post-metadata">

**Author:** ![Hitesh\_Baldaniya1](https://avatars.discourse-cdn.com/v4/letter/h/45deac/32.png) [@Hitesh\_Baldaniya1](https://discuss.elastic.co/u/Hitesh_Baldaniya1)\
**Post date:** [August 22, 2019, 7:09am UTC](https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250/3 "2019-08-22T07:09:27Z")

</div>

Hi @Christian_Dahlqvist,

Yes, that's correct behaviour.

But my questions is even after scaling to double the size. JVM pressure should be in the range of 40-55%, instead of 60 to 70%.

Does this has any thing to do with the write or indexing operations frequency? Because we have write heavy application, where the single document gets updated multiple times.

Thanks,

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 22, 2019, 7:26am UTC](https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250/4 "2019-08-22T07:26:26Z")

</div>

It will always go up to 75% before reclaiming. It is the level it goes down to after this that is important, not the current value.

---

<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:** [September 19, 2019, 7:39am UTC](https://discuss.elastic.co/t/upgrading-cluster-resource-still-the-consumptions-remains-same/196250/5 "2019-09-19T07:39:26Z")

</div>

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