[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961970#comment-14961970
]
Ramkumar Aiyengar edited comment on SOLR-7344 at 10/17/15 5:10 PM:
-------------------------------------------------------------------
[~ysee...@gmail.com], [~markrmil...@gmail.com] and I got a chance to discuss
this at Revolution. One approach we seemed to have consensus on (correct me
guys if I am wrong) is:
- We use a single, small, internal queue for non-streaming APIs.
- We leave the limit high for streaming APIs and raise a new issue for (1) The
ability to control the amount of nesting in Streaming APIs, and (2) To
dynamically have N pools (Internal.1, Internal.2, ...., Internal.N), each with
a small limit, where N is the amount of maximum nesting configured for
Streaming APIs..
was (Author: andyetitmoves):
[~ysee...@gmail.com], [~markrmil...@gmail.com] and me got a chance to discuss
this at Revolution. One approach we seem to have consensus on (correct me guys
if I am wrong) is:
- We use a single, small, internal queue for non-streaming APIs.
- We leave the limit high for streaming APIs and raise a new issue for (1) The
ability to control the amount of nesting in Streaming APIs, and (2) To
dynamically have N pools (Internal.1, Internal.2, ...., Internal.N), each with
a small limit, where N is the amount of maximum nesting configured for
Streaming APIs..
> 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
