[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578132#comment-14578132
]
Hrishikesh Gadre commented on SOLR-7344:
----------------------------------------
OK. Here is the first cut implementation of this idea
https://github.com/hgadre/servletrequest-scheduler
This is just the core logic for this approach. We still need to implement solr
specific policy to use it. I am thinking to partition the worker pool such that
we identify following types of requests,
- Internal_Querying
- Internal_Indexing
- External_Local (viz. requests sent by external clients such that a given
collection is available on this server).
- External_Forwarded (viz. requests sent by external clients such that a given
collection is not available on this server).
- Admin requests (?)
I think the tricky part here is to identify the appropriate thread-pool size
for each of the partition. Please take a look and let me know any feedback.
> 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]
