Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 8 Jun 2017 10:03:18 +0000 (UTC)
From: "Phil Yang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13064378.1492424972000.26551.1496916198653@Atlassian.JIRA>
In-Reply-To: <JIRA.13064378.1492424972000@Atlassian.JIRA>
References: <JIRA.13064378.1492424972000@Atlassian.JIRA> <JIRA.13064378.1492424972862@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (HBASE-17931) Assign system tables to
 servers with highest version
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Jun 2017 10:03:24 -0000


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

Phil Yang edited comment on HBASE-17931 at 6/8/17 10:02 AM:
------------------------------------------------------------

2.0.0-alpha will be released soon so back to this issue. org/apache/hadoop/hbase/master/AssignmentManager.java is gone so I'm going to prepare a new patch.


was (Author: yangzhe1991):
2.0.0-alpha will be released soon so back to this issue. AssignmentManager is gone so I'm going to prepare a new patch.

> 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: scan
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>            Priority: Blocker
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-17931.v01.patch, HBASE-17931.v02.patch, HBASE-17931.v03.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
(v6.3.15#6346)