[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509859#comment-14509859
]
Ramkumar Aiyengar commented on SOLR-7344:
-----------------------------------------
Right, if you want to get all this logic in, aren't you at this point doing a
part of Jetty's job? I get the motivation behind keeping a single port, but
that perhaps is also solved by having some custom classes plugged into Jetty --
which we should be free to do now. The Solr code from dispatch filter downwards
should be worried with the application logic, with the container (or whatever
network layer we are moving towards) taking care of the resource allocation.
> Use two thread pools, one for internal requests and one for external, to
> avoid distributed deadlock and decrease the number of threads that need to be
> created.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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]
