lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hrishikesh Gadre (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-7344) 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.
Date Sun, 14 Jun 2015 00:04:01 GMT

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

Hrishikesh Gadre commented on SOLR-7344:
----------------------------------------

>>It's probably not many - I think all distributed query sub-request are dispatched
via a single method for example.

Yes that may be the case for querying. But what about replication/indexing? What about admin
requests (if any)? There could be more functionality that I may be missing. Instead passing
this parameter by default make more sense as the parameter itself is harmless and this will
cover all possible functionalities. The parameter can be passed either via query string or
a header.

 

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message