Hi Jason
We are running with -XX:MaxGCPauseMillis=5000 as well, which might also
help you.
Best regards Trym
Den 11-07-2012 07:55, Jason skrev:
Actually we got this error when remote server is executing garbage collecting
and that time is over about 1 minute.
Solr server sometimes is frozen
Right, as Michael says you've allocated a massive amount of memory.
I suspect you're just hitting a full-pause garbage collection and it's
taking a lng time. Do you know whether you actually need all
that memory or was it allocated on the theory that "more is better"?
We often recommend that y
Hi, Jason,
That's a huge heap. Which Directory implementation are you using? It
might make more sense to drastically reduce that heap and let the OS
buffer the index at a lower level.
Michael Della Bitta
Appinions, Inc. -- Where Influence Isn’t a
Hi Erick
Our physical memory is 128g and jvm option is -Xms110g -Xmx110g
-XX:PermSize=512m -XX:MaxPermSize=512m
This is very huge memory allocation.
But we are servicing patent search and that is accepted very complex queries
used memory.
--
View this message in context:
http://lucene.472066.n3.
There are about a zillion garbage collection options, see:
http://www.lucidimagination.com/blog/2011/03/27/garbage-collection-bootcamp-1-0/
for a great intro.
Be a bit careful. Allocating more memory to the JVM can cause the GCs to take
a longer time when they do occur. How much memory are you allo
Actually we got this error when remote server is executing garbage collecting
and that time is over about 1 minute.
Solr server sometimes is frozen during gc and occurred connection refused
error.
Our gc option is -XX:+UseParallelGC -XX:+UseParallelOldGC
-XX:+AggressiveOpts
Response waiting is bet
