# JVM memory pressure is high only for one master node **URL:** \ **Category:** Elasticsearch\ **Created:** [October 23, 2019, 5:06pm UTC](https://discuss.elastic.co/t/jvm-memory-pressure-is-high-only-for-one-master-node/204921 "2019-10-23T17:06:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![dalakada](https://avatars.discourse-cdn.com/v4/letter/d/bbe5ce/32.png) [@dalakada](https://discuss.elastic.co/u/dalakada)\ **Post date:** [October 23, 2019, 5:06pm UTC](https://discuss.elastic.co/t/jvm-memory-pressure-is-high-only-for-one-master-node/204921/1 "2019-10-23T17:06:26Z")
Our ES cluster lives on AWS. We have 3 master nodes and 4 data nodes. But JVM memory pressure is not distributed evenly across them. 2 of them are having usually around %10 but last one is usually fixed at %60. Any reason why is this the case? ---
**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:** [October 23, 2019, 5:45pm UTC](https://discuss.elastic.co/t/jvm-memory-pressure-is-high-only-for-one-master-node/204921/2 "2019-10-23T17:45:51Z")
Garbage collection generally kicks in once heap usage reaches 75%, so as long as the heap is below this there is usually no problem. The fact that the nodes have different values may just be because they are under different load or garbage collected at different points in the past. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 20, 2019, 5:45pm UTC](https://discuss.elastic.co/t/jvm-memory-pressure-is-high-only-for-one-master-node/204921/3 "2019-11-20T17:45:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.