lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5928) WildcardQuery may has memory leak
Date Fri, 19 Sep 2014 03:17:33 GMT


Shawn Heisey commented on LUCENE-5928:

I have seen this exact memory reporting issue on my Solr installs.  Java appears to misreport
memory usage.  See how your SHR value is 37GB?  If you subtract that from your RES value,
I think that's a lot closer to how much memory it's actually using.

For what follows, reference the screenshot that I have attached.


Solr on this machine has a max heap of 6144M.  The machine has 64GB of RAM.  Let's add up
some numbers, each of which I would ordinarily consider to be absolute truth:

16GB: RES size of the Solr process.
9.8GB: The amount of memory listed as free.
44GB: The amount of memory used by the OS disk cache.
1.1GB: next largest java process.
0.3GB: next largest java process.

These numbers add up to more than 70GB ... but the machine only has 64GB total.

> WildcardQuery may has memory leak
> ---------------------------------
>                 Key: LUCENE-5928
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 4.9
>         Environment: SSD 1.5T, RAM 256G, records 15*10000*10000
>            Reporter: Littlestar
>            Assignee: Uwe Schindler
>         Attachments: idxb1-top-sorted-mem.png, top_java.jpg
> data 800G, records 15*10000*10000.
> one search thread.
> content:???
> content:*
> content:*1
> content:*2
> content:*3
> jvm heap=96G, but the jvm memusage over 130g?
> run more wildcard, use memory more....
> Does luence search/index use a lot of DirectMemory or Native Memory?
> I use -XX:MaxDirectMemorySize=4g, it does nothing better.
> Thanks.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message