You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Phil Yang (JIRA)" <ji...@apache.org> on 2017/04/17 10:29:41 UTC
[jira] [Created] (HBASE-17931) Rolling upgrade on branch-1 and
master
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 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 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
(v6.3.15#6346)