[
https://issues.apache.org/jira/browse/SOLR-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628965#comment-17628965
]
Bence Szabó commented on SOLR-16367:
------------------------------------
I have seen that we make of a {{defaultHttpClient}} from the class
{{UpdateShardHandler}} in multiple locations (for example in the
[Overseer|https://github.com/apache/solr/blob/main/solr/core/src/java/org/apache/solr/cloud/Overseer.java#L836]
or the
[ZkController|https://github.com/apache/solr/blob/main/solr/core/src/java/org/apache/solr/cloud/ZkController.java#L859])
I tried to dig into it and understand what is specific about this client and
tried to reproduce the same without using apache.http classes, but it is full
of them and I got a little lost.
Do we need such a default client or the one that is created by default with the
{{Http2SolrClient}} works just fine in these places?
> Switch from CloudLegacySolrClient to CloudSolrClient
> ----------------------------------------------------
>
> Key: SOLR-16367
> URL: https://issues.apache.org/jira/browse/SOLR-16367
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
>
> CloudLegacySolrClient is deprecated; it uses the Apache HTTP client.
> CloudSolrClient uses the Jetty HTTP client, which supports HTTP 2. In this
> issue, switch all of Solr to not use CloudLegacySolrClient anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
