[
https://issues.apache.org/jira/browse/HBASE-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988294#action_12988294
]
Jonathan Gray commented on HBASE-3373:
--------------------------------------
Round-robin assignment at table creation is fine. Bypassing the load balancer
and doing your own thing is fine. Adding intelligence into the balancer to get
good balance of load is great.
I'm -1 on adding these kinds of specialized hooks into HBase proper. They
should either be an external component (seems that they can be) or we should
make the balancer pluggable and you could provide alternative/configurable
balancer implementations.
Assigning overloaded regions in a round-robin way to underloaded does make
sense. Would be happy to take a contribution to do that. I'm not sure there's
a very strong correlation with that and splitting up of daughter regions. It
certainly could be the case, but selection of which regions to move off an
overloaded server is rather dumb so no guarantees that recently split regions
get reassigned.
> Allow regions of specific table to be load-balanced
> ---------------------------------------------------
>
> Key: HBASE-3373
> URL: https://issues.apache.org/jira/browse/HBASE-3373
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.20.6
> Reporter: Ted Yu
> Fix For: 0.92.0
>
>
> From our experience, cluster can be well balanced and yet, one table's
> regions may be badly concentrated on few region servers.
> For example, one table has 839 regions (380 regions at time of table
> creation) out of which 202 are on one server.
> It would be desirable for load balancer to distribute regions for specified
> tables evenly across the cluster. Each of such tables has number of regions
> many times the cluster size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
