You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Atri Sharma (Jira)" <ji...@apache.org> on 2020/06/25 08:10:00 UTC

[jira] [Commented] (SOLR-7344) Allow Jetty thread pool limits while still avoiding distributed deadlock.

    [ https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144735#comment-17144735 ] 

Atri Sharma commented on SOLR-7344:
-----------------------------------

Revisiting this issue.

I would like a way to define a way to balance indexing and search requests that are ingested for a given node. Ideally, the first thing that comes to mind is a QoS filter on Jetty that allows HTTP request filtering. However, given the extensive discussion that has taken place on this thread, I would want to prod this idea again and see if we can reach a consensus on a generic solution that can allow us to extend and tune for different types of requests.


> 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
>            Priority: Major
>         Attachments: SOLR-7344.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org