[
https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated HBASE-17931:
--------------------------
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> Assign system tables to servers with highest version
> ----------------------------------------------------
>
> Key: HBASE-17931
> URL: https://issues.apache.org/jira/browse/HBASE-17931
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment, scan
> Reporter: Phil Yang
> Assignee: Phil Yang
> Priority: Blocker
> Fix For: 1.4.0, 2.0.0-alpha-2, 2.0.0
>
> Attachments: HBASE-17931.branch-1.v01.patch,
> HBASE-17931.branch-1.v02.patch, HBASE-17931.branch-1.v03.patch,
> HBASE-17931.branch-1.v04.patch, HBASE-17931.branch-1.v04.patch,
> HBASE-17931.branch-1.v05.patch, HBASE-17931.branch-1.v05.patch,
> HBASE-17931.branch-1.v06.patch, HBASE-17931.v01.patch, HBASE-17931.v02.patch,
> HBASE-17931.v03.patch, HBASE-17931.v04.patch, HBASE-17931.v04.patch,
> HBASE-17931.v05.patch
>
>
> 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
(v7.6.3#76005)
