[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115075#comment-16115075
]
Varun Thacker commented on SOLR-7344:
-------------------------------------
Hi Hrishikesh,
Okay reading a bit more would this comment of yours accurately describe the
current state of work?
{quote}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.{quote}
So this Jira would add a filter , then SOLR-7683 and SOLR-7684 would actually
make use of it?
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
