[
https://issues.apache.org/jira/browse/HBASE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977199#comment-13977199
]
stack commented on HBASE-10873:
-------------------------------
Good by me. Thinking on it, I think it'd be fine to flag in a release note
that Master and BUMaster will carry full-complement of regions after upgrade
(unless you configure it to work the old way). Having this option where
*Master's carry a lighter loading would be a nice-to-have though I think it
will be little used.
[~jxiang] If we set it so backup masters should NOT carry regions, does it use
this code path -- the one in this patch?
See what [~enis] says.
> 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)
