[
https://issues.apache.org/jira/browse/SOLR-12641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578441#comment-16578441
]
Bar Rotstein commented on SOLR-12641:
-------------------------------------
Quoting elyogreg from [Jetty
#1350|https://github.com/eclipse/jetty.project/issues/1350]:
{quote}@elyograg that is correct, there is no way to do it currently. An
instance of HttpClient is created with a specific transport and currently
cannot switch to another transport.
You can partially workaround this by having two HttpClient instances, one with
the HTTP/1.1 transport and one with the HTTP/2 transport, but you have to try
one, if it fails try the other, it's clunky.
{quote}
Seems like currently the only way to to try and use the HTTP2 client, and fail
over to the HTTP1.1 client, until [issue
#1350|https://github.com/eclipse/jetty.project/issues/1350] is resolved.
> Http2SolrClient should be able to connect to old Solr nodes.
> ------------------------------------------------------------
>
> Key: SOLR-12641
> URL: https://issues.apache.org/jira/browse/SOLR-12641
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Priority: Major
>
> Right now, Http2SolrClient can't connect to old Solr nodes, this seems an
> issue of Jetty HTTP client
> (https://github.com/eclipse/jetty.project/issues/1308). To support rolling
> updates, this problem must be solved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
