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 25958200C29 for ; Tue, 14 Feb 2017 00:53:13 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 22843160B6C; Mon, 13 Feb 2017 23:53:13 +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 6A0CE160B60 for ; Tue, 14 Feb 2017 00:53:12 +0100 (CET) Received: (qmail 17535 invoked by uid 500); 13 Feb 2017 23:53:11 -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 17524 invoked by uid 99); 13 Feb 2017 23:53:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2017 23:53:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 233DFC135B for ; Mon, 13 Feb 2017 23:53:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id YUHU7QSNiFxC for ; Mon, 13 Feb 2017 23:53:10 +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 5060E5F570 for ; Mon, 13 Feb 2017 23:53:10 +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 89243E064B for ; Mon, 13 Feb 2017 23:52:42 +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 D3DC721D6C for ; Mon, 13 Feb 2017 23:52:41 +0000 (UTC) Date: Mon, 13 Feb 2017 23:52:41 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-17642) [RSGROUP] Master hosting regions messes up rsgroup calculation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Feb 2017 23:53:13 -0000 stack created HBASE-17642: ----------------------------- Summary: [RSGROUP] Master hosting regions messes up rsgroup calculation Key: HBASE-17642 URL: https://issues.apache.org/jira/browse/HBASE-17642 Project: HBase Issue Type: Bug Components: Region Assignment, rsgroup Affects Versions: 2.0.0 Reporter: stack Priority: Blocker In master branch, the Master poses as a RegionServer but it only carries hbase:meta by default. This messes up rsgroup assignment checks and calculations at an extreme when there is only one server in the default group and this server is Master. A move of all servers but this 'fake' RegionServer looks safe because there is a server to pick up all regions shed by the moved servers. All non-hbase:meta regions are dropped and put into the FAILED_OPEN state. There are a few things up here. * Master looks like a RegionServer in much of the system when we are asking for the list of online servers but it is not a full-blown regionserver; the balancer and/or AM are giving out misleading views on the cluster at least as far as rsgroup is concernd. * rsgroup shouldn't have to do assignment calculations; it should have API to ask the AM to do it for it. I'm filing this blocker and then putting it aside for now. AM is being redone currently. Will come back when it has been rejiggered. At a minimum, can add check to rsgroup but preferrably can add necessary API to AM for rsgroup to use. -- This message was sent by Atlassian JIRA (v6.3.15#6346)