[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509891#comment-14509891
]
Yonik Seeley commented on SOLR-7344:
------------------------------------
bq. The Solr code from dispatch filter downwards should be worried with the
application logic
Our DispatchFilter is the bridge between network/container and application
logic. We may be able to move more application-only code out of the dispatch
filter though.
bq. but that perhaps is also solved by having some custom classes plugged into
Jetty – which we should be free to do now.
Yep, good point. We don't have to do anything in a servlet-generic way any
more.
Whether something is implemented in the dispatch filter or in another custom
class plugged into Jetty should be determined by which is easier.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
