Look into -XX:-GCUseOverheadLimit
On 7/26/10, Jonathan Rochkind 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 a 'commit', afte
Hi,
which version do you use? 1.4.1 is highly recommended since previous versions
contained some
bugs related to memory usage that could lead to memory leaks. i had this gc
overhead limit
in my setup as well. only workaround that helped was a dayly restart of all
instances.
with 1.4.1 this iss
> 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
On Mon, Jul 26, 2010 at 7:17 PM, Jonathan Rochkind 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 of a garbage collect
