hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
Date Tue, 18 Apr 2017 03:36:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972073#comment-15972073

Phil Yang commented on HBASE-17931:

Another option is keep compatibility between client 1.4 and server 1.3, and compatibility
between client 2.0 and server 1.4. Then we can rolling upgrade from 1.3 to 1.4 and from 1.4
to 2.0. But we have to release 1.4.0 before 2.0.0. Which means we should return more results
in 1.4 server and don't have to do this in 2.0

> Rolling upgrade on branch-1 and master
> --------------------------------------
>                 Key: HBASE-17931
>                 URL: https://issues.apache.org/jira/browse/HBASE-17931
>             Project: HBase
>          Issue Type: Bug
>          Components: scan
>    Affects Versions: 1.4.0
>            Reporter: Phil Yang
>            Priority: Blocker
>             Fix For: 2.0.0
> In branch-1 and master we have some improvement and new features on scanning which is
not compatible.
> A client of old version to a server of new version is compatible (must be a bug if not,
maybe need some test?). 
> A client of new version may not be able to read from a server of old version correctly
(because of scan limit, moreResults flag, etc), which is ok for major/minor upgrade and we
can tell users to upgrade server before upgrading client. But RS also use scan to read meta.
If meta table is in RS of old version, all RSs of new version may have trouble while scanning
meta table.
> So we should make sure meta table always in servers of new version. Force meta table
in Master and upgrade Master first, or assign meta table in region servers with latest version?

This message was sent by Atlassian JIRA

View raw message