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] [Created] (HBASE-17931) Rolling upgrade on branch-1 and master
Date Mon, 17 Apr 2017 10:29:41 GMT
Phil Yang created HBASE-17931:

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

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 can not read from a server of old version, which is ok for major/minor
upgrade. 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
or assign meta table in region servers with latest version?

This message was sent by Atlassian JIRA

View raw message