[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585266#comment-14585266
]
Yonik Seeley commented on SOLR-7344:
------------------------------------
bq. The stuff Joel recently committed?
Yeah, in 5.1
bq. In any case, I still see no need for 10k limits, much better that by
default these request fail instead of eating up 10k threads.
We don't *want* 10K threads today... we have to have it (a high limit) or we'll
get into distributed deadlock. Eating up additional threads is better than
distributed deadlock, and better than arbitrarily failing requests at some low
level when the system still has resources it could use.
Just because we have an unbounded pool doesn't mean that it will be used up
under normal circumstances, it just means that we can't put a safe bound on it
without risking distributed deadlock. The real max will likely be some
function of the queue sizes of any queues that can make a request to the
unbounded queue along with the number of nodes in the system.
> Allow Jetty thread pool limits while still avoiding distributed deadlock.
> -------------------------------------------------------------------------
>
> Key: SOLR-7344
> URL: https://issues.apache.org/jira/browse/SOLR-7344
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Attachments: SOLR-7344.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
