[
https://issues.apache.org/jira/browse/SOLR-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-1941.
-----------------------------
Resolution: Cannot Reproduce
Closing old issue as cannot reproduce.
Since 5 years ago there has been several new Jetty versions and loads of
testing and optimization for multiple cores, so this is likely not a bug
(anymore).
> Jetty configuration is faulty with many cores & simultaneous requests
> ---------------------------------------------------------------------
>
> Key: SOLR-1941
> URL: https://issues.apache.org/jira/browse/SOLR-1941
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.1
> Reporter: David Smiley
>
> There is a problem with the default configuration of Jetty in the Solr trunk
> release (not present in Solr 1.4 and prior). There is a difference in the
> jetty configuration which is for the latest Solr to use the QueuedThreadPool
> (as seen in jetty.xml). Previously, it had used a BoundedThreadPool
> implementation that I've heard is considered deprecated presently. I have a
> multi-core setup where Jetty is serving up lots of Solr cores 9+ and when our
> client does a distributed search (3 of them at a time actually), it triggers
> a condition in which the query takes 50 plus seconds to respond. During this
> time, the machine is effectively idle, seemingly waiting for something. To
> fix this, go back to the former BoundedThreadPool implementation or don't use
> Jetty. FWIW this has triggered us to swtich to Tomcat.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
