[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585198#comment-14585198
]
Mark Miller commented on SOLR-7344:
-----------------------------------
bq. Job #1 should be: what will actually work best for our existing system
right now, by default, and be the least invasive to clients (without counting
internal solr code as clients).
Nothing talked about makes things any more difficult for external clients, so I
don't think that's a current concern.
bq. I see discussions of mechanisms for tagging requests, but I still don't
have an understanding of if the overall problem will be solved or not.
We are talking about tagging requests because we talked about the meat of the
problem above...
The linked to GitHub code and QosFilter type approach with queues and
continuations will work as easily as multiple thread pools will work.
> 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]
