RE: index writer closes due to OOM/heap space issue but no recovery after GC

2015-01-09 Thread Ryan, Michael F. (LNG-DAY)
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

Re: index writer closes due to OOM/heap space issue but no recovery after GC

2015-01-10 Thread Michael McCandless
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