hbase-issues mailing list archives

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

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

stack commented on HBASE-17931:
-------------------------------

Thanks for raising the flag on this one [~yangzhe1991]. Agree its a blocker.

Lets figure a receipe. Generally we'll upgrade Master first on rolling upgrade.  Could bake
into it the knowledge that it not assign hbase:meta to an old RS. Requiring users go to 1.4
first and then to 2.0 would be ok too if we had too...  Thanks.

> 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
(v6.3.15#6346)

Mime
View raw message