Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 65B1E200CB4 for ; Tue, 27 Jun 2017 11:28:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4E48F160BF6; Tue, 27 Jun 2017 09:28:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9C5EA160BDC for ; Tue, 27 Jun 2017 11:28:09 +0200 (CEST) Received: (qmail 27776 invoked by uid 500); 27 Jun 2017 09:28:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 27757 invoked by uid 99); 27 Jun 2017 09:28:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 09:28:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5D460C199E for ; Tue, 27 Jun 2017 09:28:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id cVXa9wnHFL9l for ; Tue, 27 Jun 2017 09:28:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2AF7660DAD for ; Tue, 27 Jun 2017 09:28:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5558AE0DD6 for ; Tue, 27 Jun 2017 09:28:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 533C024155 for ; Tue, 27 Jun 2017 09:28:00 +0000 (UTC) Date: Tue, 27 Jun 2017 09:28:00 +0000 (UTC) From: "Phil Yang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 27 Jun 2017 09:28:10 -0000 [ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Yang updated HBASE-17931: ------------------------------ Attachment: HBASE-17931.branch-1.v05.patch Fix failed test and address reviews > 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: 2.0.0, 1.4.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.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.4.14#64029)