this issue seems to be fixed.
-Ursprüngliche Nachricht-
Von: Jonathan Rochkind [mailto:rochk...@jhu.edu]
Gesendet: Dienstag, 27. Juli 2010 01:18
An: solr-user@lucene.apache.org
Betreff: java GC overhead limit exceeded
I am now occasionally getting a Java GC overhead limit exceeded error in my
Look into -XX:-GCUseOverheadLimit
On 7/26/10, Jonathan Rochkind rochk...@jhu.edu wrote:
I am now occasionally getting a Java GC overhead limit exceeded error
in my Solr. This may or may not be related to recently adding much
better (and more) warming querries.
I can get it when trying
I am now occasionally getting a Java GC overhead limit exceeded error
in my Solr. This may or may not be related to recently adding much
better (and more) warming querries.
I can get it when trying a 'commit', after deleting all documents in my
index, or in other cases.
Anyone run
On Mon, Jul 26, 2010 at 7:17 PM, Jonathan Rochkind rochk...@jhu.edu wrote:
I am now occasionally getting a Java GC overhead limit exceeded error in
my Solr. This may or may not be related to recently adding much better (and
more) warming querries.
When memory gets tight, the JVM kicks
Short answer: GC overhead limit exceeded means out of memory.
Aha, thanks. So the answer is just raise your Xmx/heap size, you need more
memory to do what you're doing, yeah?
Jonathan
