[
https://issues.apache.org/jira/browse/SOLR-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hrishikesh Gadre updated SOLR-7683:
-----------------------------------
Attachment: SOLR-7683.patch
Here is a preliminary patch. This patch adds following two request headers in
every request sent via HttpSolrClient.
Solr-Request-Context (informs if this request is internal vs external)
Solr-Request-Type (informs the sub-type of this request)
I have defined a sub-class of HttpSolrClient which should be used for Solr
internal communication (instead of HttpSolrClient). If this looks good, I can
investigate forbidding the usage of HttpSolrClient in the Solr core logic.
Let me know if this approach sounds reasonable.
> 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]
