lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Smith <>
Subject Re: Lucene 3.0.3 Release Date
Date Fri, 29 Oct 2010 18:36:41 GMT
  the situation where i saw this was effectively committing after every 
document update (i know, not good practice, but it is what it is)
also, i hold onto the same IW for the life of the vm (i've always found 
closing and reopening IW's while feeding to be very messy and result in 
issues, especially if disk space is low, etc)
within the span of a day or less, memory would grow to a very noticeable 
size just due to the synch hash map

i've been using the lucene-2328 patch on lucene 3.0.2 for some time now 
with no issue
obviously, i would like to back out my custom overlays (and not have to 
port them to 3.0.3)

  -- Tim

On 10/29/2010 01:35 PM, Michael McCandless wrote:
> On Fri, Oct 29, 2010 at 9:01 AM, Tim Smith<>  wrote:
>>   I suggest backporting lucene-2328 as well
>> the memory leak grows based on the number of commits
>> if you are doing extremely frequent commits, the memory leak becomes a
>> sizable loss that cannot be reclaimed without restarting and may require
>> restarting the vm on a daily basis
> Closing&  opening a new IW also reclaims the memory?
> How frequently do you commit?
> Mike
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message