lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-12641) Support rolling updates when jira/http2 get merged
Date Fri, 07 Sep 2018 07:45:00 GMT

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

Cao Manh Dat updated SOLR-12641:
--------------------------------
    Description: 
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.

  was:
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 discuss with other guys, the best solution for doing rolling updates in Solr 8.0 is
* Upgrade nodes will start with a *special flag* to indicate that they will use HTTP/1.1 as
protocol for intercommunication  Using HTTP/1.1 as default for Http2SolrClient in Solr 8.0,
therefore nodes will communicate with others using HTTP/1.1 (note that servers still accept
both HTTP/1.1 and HTTP/2 connections)
* Do rolling updates 
* When all nodes are in version 8.0, restart nodes with enabling HTTP/2 flag for Http2SolrClient,
therefore nodes will communicate with others using HTTP/2 from thereafter.


> 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
>            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


Mime
View raw message