[
https://issues.apache.org/jira/browse/SOLR-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592022#comment-14592022
]
Hrishikesh Gadre commented on SOLR-7683:
----------------------------------------
>>It's okay to do this at the HttpSolrClient level? Are we no longer worried
>>about other HttpClient usage?
I think all other implementations of SolrClient use HttpSolrClient underneath.
So we are covered from client side. On the server-side we are using
HttpSolrClient mostly. I found only one usage of CloudSolrClient for WAN
replication functionality. I think for this case, we should use client context
since the communication is not between Solrcloud nodes (assuming WAN
replications requires two separate SolrCloud instances).
Any thoughts?
> Introduce support to identify Solr internal request types
> ---------------------------------------------------------
>
> Key: SOLR-7683
> URL: https://issues.apache.org/jira/browse/SOLR-7683
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Hrishikesh Gadre
> Attachments: SOLR-7683.patch
>
>
> SOLR-7344 is introducing support to partition the Jetty worker pool to
> enforce the number of concurrent requests for various types (e.g.
> Internal_Querying, Internal_Indexing, External etc.). For this we need to
> identify requests sent between Solr servers and their types (i.e.
> Querying/Indexing etc.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
