For a system that is long running and commits every X time this can prove to be problematic eventually. And then its a matter of frequency. But, as this is a recommended design pattern for lucene (commit the IndexWriter to persist you changes periodically), its quite severe. Seems like the only solution is to close and open the writer, which is a shame. It looks like the backport is quite big and more complex, but if not, then a notice on CHANGES should be made so people will be aware of this behavior?
On Fri, Oct 29, 2010 at 7:35 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Fri, Oct 29, 2010 at 9:01 AM, Tim Smith <tsm...@attivio.com> 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: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
