[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584791#comment-14584791
]
Hrishikesh Gadre commented on SOLR-7344:
----------------------------------------
My main concern with this approach is that it would require adding this code
every place we are making HTTP call and hence it is kind of fragile. A better
alternative could be to pass a Request header for every HTTP request sent
between Solr servers. Apache HTTP client has an option to configure default
headers which would be added to each outgoing request. We will need to
configure HttpClientUtil with an additional header somehow.
ClientPNames.DEFAULT_HEADERS='http.default-headers': defines the request
headers to be sent per default with each request. This parameter expects a
value of type java.util.Collection containing Header objects.
Reference:
http://hc.apache.org/httpcomponents-client-4.2.x/tutorial/html/httpagent.html
This will help us to identify internal vs external requests. Once we identify
an internal request, can we use URI paths for further identification (querying
vs indexing) ? I think the paths are hardcoded for internal traffic. Right?
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
