[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584827#comment-14584827
]
Mark Miller commented on SOLR-7344:
-----------------------------------
bq. I think the paths are hardcoded for internal traffic. Right?
The /update handler is hard coded in ConcurrentUpdateSolrServer. I don't think
this is totally intentional currently - we allow much more expressive
configuration. I don't think it's a bad idea to lock down a known /update
handler, but I think we are still in fuzzy territory in terms of decisions on
that. The query side should not be hardcoded, you can use shard.qt or something
to change the internal handler that is hit.
bq. I guess another approach would be to have SolrHttpClient always pull out
certain parameters and put them on the URL, even for POST requests.
These names are confusing, but that's the feature I mention above.
I guess more interesting would be if we could move that impl from
HttpSolrClient to the Solr HttpClient created by HttpClientUtil (currently
returns an CloseableHttpClient impl). I don't know offhand how feasible that is
though.
> 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: [email protected]
For additional commands, e-mail: [email protected]
