I increased the maximum POST size and headerBufferSize to 10MB ; lowThreads
to 50, maxThreads to 10 and lowResourceMaxIdleTime=15000. We tried
tomcat 6 using the following Connnector settings :
Connector port=8989
protocol=HTTP/1.1
redirectPort=8443
URIEncoding=UTF-8
On Sun, Jun 12, 2011 at 9:10 PM, Johannes Goll johannes.g...@gmail.com wrote:
However, sporadically, Jetty 6.1.2X (shipped with Solr 3.1.)
sporadically throws Socket connect exceptions when executing distributed
searches.
Are you using the exact jetty.xml that shipped with the solr example
this message in context:
http://lucene.472066.n3.nabble.com/Huge-performance-drop-in-distributed-search-w-shards-on-the-same-server-container-tp2938421p2988464.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
Johannes Goll
211 Curry Ford Lane
Gaithersburg, Maryland 20878
in context:
http://lucene.472066.n3.nabble.com/Huge-performance-drop-in-distributed-search-w-shards-on-the-same-server-container-tp2938421p2988464.html
Sent from the Solr - User mailing list archive at Nabble.com.
Any ideas?
On Freitag, 13. Mai 2011 at 13:19, Frederik Kraus wrote:
One Tomcat with multicore. I have a list of about 2mio real queries that
I'm firing at the cluster with jmeter. Reason for splitting up the index in
rather small parts is that the maximum response time of 1 sec cannot be
Is that 10 different Tomcat instances or are you using multicore? How are you
testing?
On May 13, 2011, at 6:08 AM, Frederik Kraus wrote:
Hi,
I'm having some serious problems scaling the following setup:
48 CPU / Tomcat / ...
localhost/shard1
...
localhost/shard10
When using
One Tomcat with multicore. I have a list of about 2mio real queries that I'm
firing at the cluster with jmeter. Reason for splitting up the index in rather
small parts is that the maximum response time of 1 sec cannot be exceeded for
any of those queries.
On Freitag, 13. Mai 2011 at 12:57,
