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 0F81911A8E for ; Tue, 22 Apr 2014 22:08:28 +0000 (UTC) Received: (qmail 31222 invoked by uid 500); 22 Apr 2014 22:08:18 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 31154 invoked by uid 500); 22 Apr 2014 22:08:17 -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 31127 invoked by uid 99); 22 Apr 2014 22:08:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2014 22:08:16 +0000 Date: Tue, 22 Apr 2014 22:08:16 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10873) Control number of regions assigned to backup masters MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977537#comment-13977537 ] stack commented on HBASE-10873: ------------------------------- bq. Probably it's better to do some consolidation and use just the configuration in this patch? It would make this patch indispensible (smile). > Control number of regions assigned to backup masters > ---------------------------------------------------- > > Key: HBASE-10873 > URL: https://issues.apache.org/jira/browse/HBASE-10873 > Project: HBase > Issue Type: Improvement > Components: Balancer > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Fix For: 0.99.0 > > Attachments: hbase-10873.patch, hbase-10873_v2.patch > > > By default, a backup master is treated just like another regionserver. So it can host as many regions as other regionserver does. When the backup master becomes the active one, region balancer needs to move those user regions on this master to other region servers. To minimize the impact, it's better not to assign too many regions on backup masters. It may not be good to leave the backup masters idle and not host any region either. > We should make this adjustable so that users can control how many regions to assign to each backup master. -- This message was sent by Atlassian JIRA (v6.2#6252)