# Elasticsearch lareg heap usage

**URL:** https://discuss.elastic.co/t/elasticsearch-lareg-heap-usage/23653
**Category:** Elasticsearch
**Created:** [May 20, 2015, 2:10pm UTC](https://discuss.elastic.co/t/elasticsearch-lareg-heap-usage/23653 "2015-05-20T14:10:23Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)
#### Post date: [May 20, 2015, 2:10pm UTC](https://discuss.elastic.co/t/elasticsearch-lareg-heap-usage/23653/1 "2015-05-20T14:10:23Z")

</div>

Hi, running...

ES 1.5.2  
Java 1.8\_45  
Windows 2008  
4 nodes of: 32 cores 128GB 5 TB SSDs (each)

ES\_HEAP\_SIZE configured to 30g

I just finished bulk indexing 350,000,000 records but all 4 nodes are  
consumming 60% heap usage and not collecting. I have your kit running on 1  
node and I tried forcing GC but nothing went down.  
I know disable explicit GC is turned on in the .bat files but with your kit  
I'm still able to force collection. I was able to collect some memory  
before.

Here is what is in the logs when I force GC from yourkit...

[ES xxx 01-01 (xxxx)] [gc][young][87406][39154] duration [1.6s],  
collections [1]/[2.5s], total [1.6s]/[17h], memory  
[18.1gb]-\>[17.1gb]/[30gb], all\_pools {[young]  
[1gb]-\>[32mb]/[0b]}{[survivor] [112mb]-\>[128mb]/[0b]}{[old]  
[16.9gb]-\>[16.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][87489][39155] duration [1.6s],  
collections [1]/[1.8s], total [1.6s]/[17h], memory  
[18.4gb]-\>[17.1gb]/[30gb], all\_pools {[young]  
[1.3gb]-\>[0b]/[0b]}{[survivor] [128mb]-\>[128mb]/[0b]}{[old]  
[16.9gb]-\>[16.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][old][87496][3] duration [43.2s], collections  
[1]/[44.2s], total [43.2s]/[1.3m], memory [17.2gb]-\>[14.9gb]/[30gb],  
all\_pools {[young] [136mb]-\>[0b]/[0b]}{[survivor] [128mb]-\>[0b]/[0b]}{[old]  
[16.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][87576][39156] duration [1.6s],  
collections [1]/[2.7s], total [1.6s]/[17h], memory [16.3gb]-\>[15gb]/[30gb],  
all\_pools {[young] [1.3gb]-\>[0b]/[0b]}{[survivor] [0b]-\>[80mb]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][87680][39157] duration [1.5s],  
collections [1]/[2.1s], total [1.5s]/[17h], memory  
[16.3gb]-\>[14.9gb]/[30gb], all\_pools {[young]  
[1.3gb]-\>[0b]/[0b]}{[survivor] [80mb]-\>[32mb]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][87770][39158] duration [1.6s],  
collections [1]/[1.9s], total [1.6s]/[17h], memory  
[16.4gb]-\>[14.9gb]/[30gb], all\_pools {[young]  
[1.4gb]-\>[0b]/[0b]}{[survivor] [32mb]-\>[24mb]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][87861][39159] duration [1.7s],  
collections [1]/[2.7s], total [1.7s]/[17h], memory  
[16.4gb]-\>[14.9gb]/[30gb], all\_pools {[young]  
[1.4gb]-\>[0b]/[0b]}{[survivor] [24mb]-\>[24mb]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][87953][39160] duration [1.5s],  
collections [1]/[1.9s], total [1.5s]/[17h], memory  
[16.3gb]-\>[14.9gb]/[30gb], all\_pools {[young]  
[1.3gb]-\>[0b]/[0b]}{[survivor] [24mb]-\>[24mb]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][young][88043][39161] duration [1.6s],  
collections [1]/[1.9s], total [1.6s]/[17h], memory  
[16.4gb]-\>[14.9gb]/[30gb], all\_pools {[young]  
[1.4gb]-\>[0b]/[0b]}{[survivor] [24mb]-\>[32mb]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}  
[ES xxx 01-01 (xxxx)] [gc][old][88079][4] duration [37.9s], collections  
[1]/[38.1s], total [37.9s]/[2m], memory [15.5gb]-\>[14.9gb]/[30gb],  
all\_pools {[young] [544mb]-\>[8mb]/[0b]}{[survivor] [32mb]-\>[0b]/[0b]}{[old]  
[14.9gb]-\>[14.9gb]/[30gb]}

As you can see I forced it twice and not much got collected...

Is it the memory mapped files that are taking up the space? Right now the  
cluster is idle.

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2ef10ae2-a95c-4c63-a9b8-6bc050d48508%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2ef10ae2-a95c-4c63-a9b8-6bc050d48508%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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: [July 6, 2017, 12:13am UTC](https://discuss.elastic.co/t/elasticsearch-lareg-heap-usage/23653/2 "2017-07-06T00:13:02Z")

</div>


