[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585261#comment-14585261
]
Mark Miller commented on SOLR-7344:
-----------------------------------
bq. Streaming API
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. Sure, you should be able
to raise the limits to eat up whatever you want. But by default, we should
really operate reasonably - if someone is doing enough recursive calls to use
up 10k threads, by default I'd rather those querys end up being denied and the
user has to consider what is going on. A default of just eating up all the
resources is *exactly* what we are trying to get away from.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
