[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586321#comment-14586321
]
Ramkumar Aiyengar commented on SOLR-7344:
-----------------------------------------
bq. It's not infinite, and it shouldn't even be high. It's just that you don't
know ahead of time what the upper bound will be because it's expressed in the
request. Even 3 levels would mess us up if the majority of the traffic
consisted of those types of requests ...
Right, rather than having a solution which solves this issue for N levels (N >
2), I am curious if it's too restrictive to say that solutions should try to
work with N = 2? From a user's perspective as well, it will be a lot easier to
predictively allocate resources if we get to that place..
> 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]
