lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan, Michael F. (LNG-DAY)" <>
Subject RE: index writer closes due to OOM/heap space issue but no recovery after GC
Date Fri, 09 Jan 2015 21:28:06 GMT
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.


From: Tom Burton-West []
Sent: Friday, January 09, 2015 4:04 PM
Subject: index writer closes due to OOM/heap space issue but no recovery after GC


I'm testing Solr 4.10.2 with 4GB allocated to the heap.  During the indexing process I get
an error message that says it is caused by an "already closed indexwriter" due to an OOM.
(See below).   After this occurs it looks like the GC kicks in and there is plenty of heap
space(see attached)  but I continue getting this error.

Can someone please explain why after the GC frees memory, I continue to get the error?

p.s. My documents average about 800KB and at completion each shard has over 3 billion unique

Tom Burton-West

 org.apache.solr.common.SolrException; org.apache.solr.common.SolrException: Exception writing
document id pst.000052087387 to the index; possible analysis error.        at og.apache.solr.update.DirectUpdateHandler2.addDoc(
caused by: this IndexWriter is closed
        at org.apache.lucene.index.IndexWriter.ensureOpen(

caused by
Caused by: java.lang.OutOfMemoryError: Java heap space
        at org.apache.lucene.index.FreqProxTermsWriterPerField$FreqProxPostingsArray.<init>(

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message