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 03D5A200C20 for ; Sun, 5 Feb 2017 06:45:47 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0277D160B63; Sun, 5 Feb 2017 05:45:47 +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 4D873160B66 for ; Sun, 5 Feb 2017 06:45:46 +0100 (CET) Received: (qmail 18001 invoked by uid 500); 5 Feb 2017 05:45:45 -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 17990 invoked by uid 99); 5 Feb 2017 05:45:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Feb 2017 05:45:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 036401812DF for ; Sun, 5 Feb 2017 05:45:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 7VRj92mAk45e for ; Sun, 5 Feb 2017 05:45:44 +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 093C05F3BE for ; Sun, 5 Feb 2017 05:45:44 +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 E9A9BE0591 for ; Sun, 5 Feb 2017 05:45: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 DC4C425292 for ; Sun, 5 Feb 2017 05:45:41 +0000 (UTC) Date: Sun, 5 Feb 2017 05:45:41 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17350) Fixup of regionserver group-based assignment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 05 Feb 2017 05:45:47 -0000 [ https://issues.apache.org/jira/browse/HBASE-17350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853120#comment-15853120 ] stack commented on HBASE-17350: ------------------------------- Added a new rsgroup component [~toffer] (good idea) > Fixup of regionserver group-based assignment > -------------------------------------------- > > Key: HBASE-17350 > URL: https://issues.apache.org/jira/browse/HBASE-17350 > Project: HBase > Issue Type: Sub-task > Components: regionserver, rsgroup > Reporter: stack > Assignee: stack > Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-17350.master.001.patch, HBASE-17350.master.002.patch, HBASE-17350.master.003.patch, HBASE-17350.master.004.patch > > > Can we do some fixup on the regionserver group-based assignement before it makes it into a release? Here are a few items after trying to use it last night: > + The commands are named inconsistently. Usually it is verb with a rsgroup suffix but we have get_table_rsgroups and then move_rsgoup_tables. Ditto for servers. > + In local mode, the regionserver doesn't belong to a group. Shouldn't it? > + Adding a server to a group with the move_rsgroup_tables is non-intuitive, to me at least (especially given #2 above). > + The error message you get when you run one of these rsgroup commands should tell you how to set up rsgroups rather than dump out a cryptic exception. > Thats all for now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)