: Rahul R [mailto:rahul.s...@gmail.com]
> Sent: August-19-09 6:19 AM
> To: solr-user@lucene.apache.org
> Subject: Re: JVM Heap utilization & Memory leaks with Solr
>
> Fuad,
> We have around 5 million documents and around 3700 fields. All documents
> will not have values for al
refer dedicated box for SOLR.
-Fuad
-Original Message-
From: Rahul R [mailto:rahul.s...@gmail.com]
Sent: August-19-09 6:19 AM
To: solr-user@lucene.apache.org
Subject: Re: JVM Heap utilization & Memory leaks with Solr
Fuad,
We have around 5 million documents and around 3700 fields. All docum
Fuad,
We have around 5 million documents and around 3700 fields. All documents
will not have values for all the fields JRockit is not approved for use
within my organization. But thanks for the info anyway.
Regards
Rahul
On Tue, Aug 18, 2009 at 9:41 AM, Funtick wrote:
>
> BTW, you should re
BTW, you should really prefer JRockit which really rocks!!!
"Mission Control" has necessary toolongs; and JRockit produces _nice_
exception stacktrace (explaining almost everything) in case of even OOM
which SUN JVN still fails to produce.
SolrServlet still catches "Throwable":
} catch (Th
;> (at least!)
>>
>>
>> I didn't notice any memory leaks after I started to use 16Gb RAM for SOLR
>> instance (almost a year without any restart!)
>>
>>
>>
>>
>> -Original Message-
>> From: Rahul R [mailto:rahul.s...@gmail.com]
>&g
t least!)
>
>
> I didn't notice any memory leaks after I started to use 16Gb RAM for SOLR
> instance (almost a year without any restart!)
>
>
>
>
> -Original Message-
> From: Rahul R [mailto:rahul.s...@gmail.com]
> Sent: August-13-09 1:25 AM
> To: solr-u
ugust-13-09 1:25 AM
To: solr-user@lucene.apache.org
Subject: Re: JVM Heap utilization & Memory leaks with Solr
*You should try to generate heap dumps and analyze the heap using a tool
like the Eclipse Memory Analyzer. Maybe it helps spotting a group of
objects holding a large amount of memory*
*You should try to generate heap dumps and analyze the heap using a tool
like the Eclipse Memory Analyzer. Maybe it helps spotting a group of
objects holding a large amount of memory*
The tool that I used also allows to capture heap snap shots. Eclipse had a
lot of pre-requisites. You need to appl
Rahul R schrieb:
> I tried using a profiling tool - Yourkit. The trial version was free for 15
> days. But I couldn't find anything of significance.
You should try to generate heap dumps and analyze the heap using a tool
like the Eclipse Memory Analyzer. Maybe it helps spotting a group of
objects
Otis,
Thank you for your response. I know there are a few variables here but the
difference in memory utilization with and without shards somehow leads me to
believe that the leak could be within Solr.
I tried using a profiling tool - Yourkit. The trial version was free for 15
days. But I couldn't
Hi Rahul,
A) There are no known (to me) memory leaks.
I think there are too many variables for a person to tell you what exactly is
happening, plus you are dealing with the JVM here. :)
Try jmap -histo:live PID-HERE | less and see what's using your memory.
Otis
--
Sematext is hiring -- http://s
11 matches
Mail list logo