Following is histogram of java object heap, dumped using jmap -histo
num #instances #bytes class name
----------------------------------------------
1: 1888557 4767284496 [B
2: 198190 1892640192 [S
3: 256130 1546754512 [I
4: 119853 1198288048 [J
5: 230881 121272272 [Lorg.apache.lucene.util.fst.FST$Arc;
6: 1391854 93015760 [C
7: 842721 60675912 org.apache.lucene.util.fst.FST$Arc
8: 1122220 35911040 java.util.HashMap$Entry
9: 1329252 31902048 java.lang.String
10: 690285 27611400 java.util.TreeMap$Entry
11: 1133480 27203520 org.apache.lucene.util.BytesRef
12: 283533 26415040 [Ljava.util.HashMap$Entry;
13: 229605 23878920 org.apache.lucene.util.fst.FST
14: 259069 18856896 [Ljava.lang.Object;
15: 229603 16531416
org.apache.lucene.codecs.BlockTreeTermsReader$FieldReader
16: 266852 14943712 java.util.HashMap
17: 230422 11060256 org.apache.lucene.index.FieldInfo
On Thursday, February 13, 2014 10:19:28 AM UTC-5, Ankush Jhalani wrote:
>
> We have a single node, 12GB, 16 core ES instance to which we are 12
> threads bulk indexing into a 12shard index. Each thread sends a request of
> size kb to couple megabytes. The thread bulk queue_size is increased from
> default 50 to 100.
>
> With v0.90.11, we are noticing that the jvm memory usage keeps growing
> slowly and doesn't go down, gc runs frequently but doesn't free up much
> memory. From debug logs, it seems the segment merges are happening. However
> even after we stop indexing, for many hours the instance is busy doing
> segment merges. Sample gist from hot threads I ran couple minutes apart - (
> https://gist.github.com/ajhalani/8976792). Even after 16 hours and little
> use on the machine, the jvm memory usage is about 80% (CMS should run at
> 75%) and nodes stats show is running very frequently.
>
> If we don't stop indexing, eventually after 60-70GB indexing the instance
> goes out of memory. This seems like a memory leak, we didn't face this
> issue with 0.90.7 (though we were probably using a 6 thread process for
> bulk indexing).
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/c60091b9-52e2-4b3e-9456-25985e80c1d5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.