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

["Mark Miller (JIRA)" <ji...@apache.org>]

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

Mark Miller commented on SOLR-7344:
-----------------------------------

bq. Yes that may be the case for querying. But what about replication/indexing? 

These requests can already be internal / external and will require the same attention if you use headers. Perhaps I'm not understanding, but I'm not sure a default of internal / external gains you much - you still have to consider each call. We use SolrJ clients that are both user and internal based and HttpClients are in the same boat. How will that param default to the right value? Sure, you can always populate it by default - who cares if it's the wrong value?

bq. What about admin requests (if any)?

All admin requests *should* be easily identifiable by URL. The std Admin request handlers location are purposely hardcoded in SolrCloud mode.

> 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.3.4#6332)

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