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 75C5A200BEF for ; Tue, 20 Dec 2016 08:20:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7316D160B1B; Tue, 20 Dec 2016 07:20:01 +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 C4418160B34 for ; Tue, 20 Dec 2016 08:20:00 +0100 (CET) Received: (qmail 1273 invoked by uid 500); 20 Dec 2016 07:19:59 -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 1141 invoked by uid 99); 20 Dec 2016 07:19:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2016 07:19:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 310392C2A66 for ; Tue, 20 Dec 2016 07:19:59 +0000 (UTC) Date: Tue, 20 Dec 2016 07:19:59 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-6721) RegionServer Group based Assignment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 20 Dec 2016 07:20:01 -0000 [ https://issues.apache.org/jira/browse/HBASE-6721?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6721: ------------------------- Release Note:=20 [ADVANCED USERS ONLY] This patch adds a new experimental module hbase-rsgro= up. It is an advanced feature for partitioning regionservers into distincti= ve groups for strict isolation, and should only be used by users who are so= phisticated enough to understand the full implications and have a sufficien= t background in managing HBase clusters.=20 RSGroups can be defined and managed with shell commands or corresponding Ja= va APIs. A server can be added to a group with hostname and port pair, and = tables can be moved to this group so that only regionservers in the same rs= group can host the regions of the table. RegionServers and tables can only = belong to 1 group at a time. By default, all tables and regionservers belon= g to the "default" group. System tables can also be put into a group using = the regular APIs. A custom balancer implementation tracks assignments per r= sgroup and makes sure to move regions to the relevant regionservers in that= group. The group information is stored in a regular HBase table, and a zoo= keeper-based read-only cache is used at the cluster bootstrap time.=20 To enable, add the following to your hbase-site.xml and restart your Master= : {code} hbase.coprocessor.master.classes org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint hbase.master.loadbalancer.class org.apache.hadoop.hbase.rsgroup.RSGroupBasedLoadBalancer {code} Then use the shell 'rsgroup' commands to create and manipulate regionserver= groups: e.g. to add a group and then add a server to it, do as follows: {code} hbase(main):008:0> add_rsgroup 'my_group' Took 0.5610 seconds {code} This adds a group to the 'hbase:rsgroup' system table. Add a server (hostna= me + port) to the group using the 'move_rsgroup_servers' command as follows= : {code} move_rsgroup_servers 'my_group',['k.att.net:51129'] {code} was: [ADVANCED USERS ONLY] This patch adds a new experimental module hbase-rsgro= up. It is an advanced feature for partitioning regionservers into distincti= ve groups for strict isolation, and should only be used by users who are so= phisticated enough to understand the full implications and have a sufficien= t background in managing HBase clusters.=20 RSGroups can be defined and managed with shell commands or corresponding Ja= va APIs. A server can be added to a group with hostname and port pair, and = tables can be moved to this group so that only regionservers in the same rs= group can host the regions of the table. RegionServers and tables can only = belong to 1 group at a time. By default, all tables and regionservers belon= g to the "default" group. System tables can also be put into a group using = the regular APIs. A custom balancer implementation tracks assignments per r= sgroup and makes sure to move regions to the relevant regionservers in that= group. The group information is stored in a regular HBase table, and a zoo= keeper-based read-only cache is used at the cluster bootstrap time.=20 > RegionServer Group based Assignment > ----------------------------------- > > Key: HBASE-6721 > URL: https://issues.apache.org/jira/browse/HBASE-6721 > Project: HBase > Issue Type: New Feature > Components: regionserver > Reporter: Francis Liu > Assignee: Francis Liu > Labels: hbase-6721 > Fix For: 2.0.0 > > Attachments: 6721-master-webUI.patch, HBASE-6721 GroupBasedLoadBa= lancer Sequence Diagram.xml, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.p= df, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721_0.98_2.pat= ch, HBASE-6721_10.patch, HBASE-6721_11.patch, HBASE-6721_12.patch, HBASE-67= 21_13.patch, HBASE-6721_14.patch, HBASE-6721_15.patch, HBASE-6721_8.patch, = HBASE-6721_9.patch, HBASE-6721_9.patch, HBASE-6721_94.patch, HBASE-6721_94.= patch, HBASE-6721_94_2.patch, HBASE-6721_94_3.patch, HBASE-6721_94_3.patch,= HBASE-6721_94_4.patch, HBASE-6721_94_5.patch, HBASE-6721_94_6.patch, HBASE= -6721_94_7.patch, HBASE-6721_98_1.patch, HBASE-6721_98_2.patch, HBASE-6721_= hbase-6721_addendum.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, = HBASE-6721_trunk.patch, HBASE-6721_trunk1.patch, HBASE-6721_trunk2.patch, b= alanceCluster Sequence Diagram.svg, hbase-6721-v15-branch-1.1.patch, hbase-= 6721-v16.patch, hbase-6721-v17.patch, hbase-6721-v18.patch, hbase-6721-v19.= patch, hbase-6721-v20.patch, hbase-6721-v21.patch, hbase-6721-v22.patch, hb= ase-6721-v23.patch, hbase-6721-v25.patch, hbase-6721-v26.patch, hbase-6721-= v26_draft1.patch, hbase-6721-v27.patch, hbase-6721-v27.patch, hbase-6721-v2= 7.patch.txt, hbase-6721-v28.patch, hbase-6721-v28.patch, hbase-6721-v29.pat= ch, immediateAssignments Sequence Diagram.svg, randomAssignment Sequence Di= agram.svg, retainAssignment Sequence Diagram.svg, roundRobinAssignment Sequ= ence Diagram.svg > > > In multi-tenant deployments of HBase, it is likely that a RegionServer wi= ll be serving out regions from a number of different tables owned by variou= s client applications. Being able to group a subset of running RegionServer= s and assign specific tables to it, provides a client application a level o= f isolation and resource allocation. > The proposal essentially is to have an AssignmentManager which is aware o= f RegionServer groups and assigns tables to region servers based on groupin= gs. Load balancing will occur on a per group basis as well.=20 > This is essentially a simplification of the approach taken in HBASE-4120.= See attached document. -- This message was sent by Atlassian JIRA (v6.3.4#6332)