[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493789#comment-14493789
]
Ramkumar Aiyengar commented on SOLR-7344:
-----------------------------------------
Thanks for getting to this Hrishikesh, we had been meaning to do this
ourselves. I personally would prefer the choice of pool to be configurable
rather than enforced.
Also, I think the idea of external/internal should be generalized especially if
we are thinking of changing the ZK information. In general, you have a set of
named pools which can be configured, and each action in Solr (we could start
with internal/external here, but this could be made more granular if needed,
say, on a request type basis for example) could run off a pool name which is
configurable.
> 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
>
--
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
