Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 22 Nov 2016 13:21:59 +0000 (UTC)
From: "Yu Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13022439.1479805361000.338909.1479820919475@Atlassian.JIRA>
In-Reply-To: <JIRA.13022439.1479805361000@Atlassian.JIRA>
References: <JIRA.13022439.1479805361000@Atlassian.JIRA> <JIRA.13022439.1479805361299@arcas>
Subject: [jira] [Updated] (HBASE-17159) Improve the assignment plan when
 server aborted or creating tables, etc.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 22 Nov 2016 13:22:01 -0000


     [ https://issues.apache.org/jira/browse/HBASE-17159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yu Li updated HBASE-17159:
--------------------------
    Summary: Improve the assignment plan when server aborted or creating tables, etc.  (was: Better the Assignment plan when server aborted or creating tables, etc.)

> Improve the assignment plan when server aborted or creating tables, etc.
> ------------------------------------------------------------------------
>
>                 Key: HBASE-17159
>                 URL: https://issues.apache.org/jira/browse/HBASE-17159
>             Project: HBase
>          Issue Type: New Feature
>          Components: Balancer, Region Assignment
>    Affects Versions: 2.0.0, 1.2.4
>            Reporter: Charlie Qiangeng Xu
>
> When master processing a dead serve or creating a new table, the assignment plan would be generated based on the roundRobinAssignment method of balancer.
> Yet if these operations happen a lot, the cluster would be out of balance both on table level and server level. Balancer would be triggered and may cause huge amount of region moves( This is what we observed).
> Ideally, the assignment should be able to consider the table or cluster level balance as well as locality(for the case of dead server). 
>  


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)