no Jetty here (yet).
Thanks
Markus
-Original message-
From:Yonik Seeley yo...@lucidimagination.com
Sent: Tue 07-Aug-2012 23:54
To: solr-user@lucene.apache.org
Subject: Re: null:java.lang.RuntimeException: [was class
java.net.SocketTimeoutException] null
Could
Subject: RE: null:java.lang.RuntimeException: [was class
java.net.SocketTimeoutException] null
Jack,
There are no peculiarities in the JVM graphs. Only increase in used threads
and GC time. Heap space is collected quickly and doesn't suddenly increase.
There's only 256MB available
A signicant detail is the batch size which we set to 64 documents due to
earlier memory limitations. We index segments of roughly 300-500k records each
time. Lowering the batch size to 32 lead to an early internal server error and
the stack trace below. Increasing it to 128 allowed us to index
Could this be just a simple case of a socket timeout? Can you raise
the timout on request threads in Tomcat?
It's a lot easier to reproduce/diagnose stuff like this when people
use the stock jetty server shipped with Solr.
-Yonik
http://lucidimagination.com
On Tue, Aug 7, 2012 at 5:39 PM,
-Original message-
From:Yonik Seeley yo...@lucidimagination.com
Sent: Tue 07-Aug-2012 23:54
To: solr-user@lucene.apache.org
Subject: Re: null:java.lang.RuntimeException: [was class
java.net.SocketTimeoutException] null
Could this be just a simple case of a socket timeout? Can you raise
