# What causes high node Heap Memory more than 75%? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 6, 2019, 10:21am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741 "2019-05-06T10:21:43Z")\ **Posts on this page:** 10\ **Page:** 1
**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:** [May 6, 2019, 10:21am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/1 "2019-05-06T10:21:44Z")
Hi Team, I am receiving high memory alerts on our cluster, we are hosted on "[cloud.elastic.co](http://cloud.elastic.co)". 3 Nodes - 2 (data/master eligible node) + 1 tie breaker node. Total 28 GB of data on a single index which has 5 shards and 1 replica set. Along with causes could you also help me finding out solution of what should be our next steps in such a situation? Thanks, ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [May 6, 2019, 10:38am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/2 "2019-05-06T10:38:14Z")
What is the output of: ```auto GET /_cat/health?v GET /_cat/indices?v GET /_cat/shards?v ``` ---
**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:** [May 6, 2019, 12:04pm UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/3 "2019-05-06T12:04:10Z")
What is the size of the cluster? Are you using nested documents and/or parent-child relationships? ---
**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:** [May 6, 2019, 12:19pm UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/4 "2019-05-06T12:19:31Z")
@Christian_Dahlqvist We are using nested documents heavily as we have such use case. Cluster size AFAIK it is 8GB RAM 2 Data node and 1 tiebreaker node. @dadoonet I have limited access to the Kibana but I am surely going to share requested details. But in a meanwhile can you brief me what sort of those parameters will help to isolate the issue? ---
**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:** [May 20, 2019, 7:43am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/5 "2019-05-20T07:43:15Z")
Hello @dadoonet, **Health** is showing normal in green state with 7 shards one 3 indexes. **Indices** - 1 for kibana, 1 for security and 1 is our production instance, total 3. **Shards** - All shards evenly distributed on both the nodes but I see few shards are heavily used while other are not much in use. Let me know your inputs based on above parameters. Hey @Christian_Dahlqvist, Did you get chance to look into above situation? Let me know if you have any inputs. Thanks, ---
**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:** [May 20, 2019, 8:39am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/6 "2019-05-20T08:39:45Z")
Nested documents use more heap that flat documents, but I do not have any figures. Will have to leave that for someone with more experience of that to comment. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [May 20, 2019, 8:48am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/7 "2019-05-20T08:48:18Z")
> [@Hitesh\_Baldaniya1](#): > > Let me know your inputs based on above parameters. I'd like to see the outputs of the commands please. Did you try to get support from [https://www.elastic.co/cloud/as-a-service/support](https://www.elastic.co/cloud/as-a-service/support) ? ---
**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:** [May 20, 2019, 8:54am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/8 "2019-05-20T08:54:01Z")
Thanks @Christian_Dahlqvist appreciate your help. ---
**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:** [May 20, 2019, 9:26am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/9 "2019-05-20T09:26:57Z")
Hi @dadoonet, We talked to our support team, but as it is basic support we are not getting actual reasons from team. Regarding output of commands I am checking with my DevOps team as it is production sensitive so not sure about sharing it. What parameters will you think of getting more meory? - Segment merging - Large no. of nested documents - GC run I wanted to know which parameters causes this kind of issues, from monitoring chart I am not able to co-relate the patterns of high CPU usage. Let me know if you have any suggetions. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2019, 9:26am UTC](https://discuss.elastic.co/t/what-causes-high-node-heap-memory-more-than-75/179741/10 "2019-06-17T09:26:59Z")
Closed on June 17, 2019, 9:26am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.