Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B6A7318A66 for ; Thu, 7 Jan 2016 12:20:40 +0000 (UTC) Received: (qmail 10737 invoked by uid 500); 7 Jan 2016 12:20:40 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 10679 invoked by uid 500); 7 Jan 2016 12:20:40 -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 10416 invoked by uid 99); 7 Jan 2016 12:20:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2016 12:20:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 05F982C1F5C for ; Thu, 7 Jan 2016 12:20:40 +0000 (UTC) Date: Thu, 7 Jan 2016 12:20:40 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 [ https://issues.apache.org/jira/browse/HBASE-6721?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1508= 7285#comment-15087285 ]=20 Enis Soztutar commented on HBASE-6721: -------------------------------------- With this patch, the RS groups is completely optional and non-core. I don't= think having the code in a different module helps in any way. =20 The patch corresponds to the plan that Francis put up here: https://issues.= apache.org/jira/browse/HBASE-6721?focusedCommentId=3D14728516&page=3Dcom.at= lassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14728516= . I thought there was an agreement already for this. We did not talk about = having a different module in that.=20 > RegionServer Group based Assignment > ----------------------------------- > > Key: HBASE-6721 > URL: https://issues.apache.org/jira/browse/HBASE-6721 > Project: HBase > Issue Type: New Feature > Reporter: Francis Liu > Assignee: Francis Liu > Labels: hbase-6721 > 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, immediateAssignments Sequence Dia= gram.svg, randomAssignment Sequence Diagram.svg, retainAssignment Sequence = Diagram.svg, roundRobinAssignment Sequence 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)