[
https://issues.apache.org/jira/browse/SOLR-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631081#comment-17631081
]
Bence Szabó commented on SOLR-16367:
------------------------------------
Just as I posted this comment I have realised that I am running into this
problem in the {{HealthcheckTool}} embedded class [0]. For this purpose I could
send a {{HealthCheckRequest}} to the new client, but as I have seen the
{{HealthCheckRequest}} checks the health of a node, but the {{HealthcheckTool}}
checks the health of a specific collection and does a bit more checks on that
one than the {{{}HealthCheckRequest{}}}.
Do you think this request class could be useful for me anyways?
[0]
[https://github.com/apache/solr/blob/640221a6ada310eae22af28e10a9c6342420898c/solr/core/src/java/org/apache/solr/util/SolrCLI.java#L1272]
> 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]
