IW closes itself on "tragic" events like OOME to guard against index
corruption
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jan 9, 2015 at 4:04 PM, Tom Burton-West wrote:
> Hello,
>
> I'm testing Solr 4.10.2 with 4GB allocated to the heap. During the indexing
> process I get an
I’m not sure about this particular error, but in general, once the JVM has
OOM’d, it is completely unreliable and should be restarted. I’m assuming Lucene
catches the OOM just so that it doesn’t get in a state where it will corrupt
the index.
-Michael
From: Tom Burton-West [mailto:tburt...@umi
Hi Josh,
Can you paste your sourcecode AND explain what are you trying to do?
Ralf
From: Josh Am [mailto:josh22...@gmail.com]
Sent: Montag, 29. August 2011 12:39
To: java-user@lucene.apache.org
Subject: Index Writer()
Dear friends Hi!!
I used Lucene to index some documents but unfo
Previously, they were not freed, just reused.
As of the tips of 29x, 30x, 3x, trunk, they are now fully freed.
Mike
On Sat, Jun 5, 2010 at 7:33 AM, Shay Banon wrote:
> I will check, just wanted to verify though, do they get freed when calling
> commit, or do they still hang around? Other pools
I will check, just wanted to verify though, do they get freed when calling
commit, or do they still hang around? Other pools are freed when calling
commit, right?
-shay.banon
On Sat, Jun 5, 2010 at 12:55 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> They are reclaimed, but, you ma
They are reclaimed, but, you may be hitting one of the memory leak
bugs recently fixed but not yet (though soon to be) released.
Can you try running with the tip of whichever release you are using?
Mike
On Fri, Jun 4, 2010 at 10:10 PM, Shay Banon wrote:
> Hi,
>
> I have a question on how Index
