[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585247#comment-14585247
]
Mark Miller commented on SOLR-7344:
-----------------------------------
bq. Since QoSFilter does not directly solve the deadlock issue
Meh - I think anyone reading or following this issue should check out the
QosFilter.java code. It's a much more solid foundational reference point due to
it's documentation, origins with the Jetty team, and as it's not a new creation.
bq. I assumed that at least some queues would be (essentially) unbounded (like
our 10K today) to solve all of the distributed deadlock problems.
Okay, well that is something concrete :) I don't want any unboundedness in this
issue - it's been one of my primary goals since I started considering two
thread pools.
bq. streaming API already has the ability to make unlimited recursive requests.
The stuff Joel recently committed?
> 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]
