[jira] [Resolved] (SOLR-12641) Support rolling updates when jira/http2 get merged

["Cao Manh Dat (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-12641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cao Manh Dat resolved SOLR-12641.
---------------------------------
    Resolution: Fixed
      Assignee: Cao Manh Dat

> Support rolling updates when jira/http2 get merged
> --------------------------------------------------
>
>                 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
>            Assignee: 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.
> After discussing with other guys, we agree that rolling updates can be no support in Solr 8.0 with *default settings* since it is a major release. Users who want to do rolling updates must follow these two steps.
> * Upgrade nodes will start with a *special flag* to indicate that they will use HTTP/1.1 as the protocol for intercommunication.
> * When all nodes are in version 8.0, restart nodes and remove above *special flag*, therefore nodes will communicate with others using HTTP/2 from thereafter.
> This issue will aim to introduce that *special flag*. Note that by default HTTP/2 still the *default protocol* for Solr 8.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org