[
https://issues.apache.org/jira/browse/HBASE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975974#comment-13975974
]
stack commented on HBASE-10873:
-------------------------------
bq. I was thinking of setting the value to 0, which gives us the 0.98- behavior
of backup masters not hosting any regions. If users want to use extra capacity
they can enable this setting manually.
I suggest we let this issue in and then elsewhere discuss what 1.0 rolls out
with elsewhere -- in subtask on the 1.0 issue.
I'd be in favor of master and backup masters carrying full complement of
regions in 1.0 (if we can ensure that the master handlers are processed ahead
of any others); i.e. more radical than Jimmy has it his adding support for
master and backup masters carrying 'light' loadings. Sounds like you'd like
us to replicate the old deploy layout [~enis] but with option to move to the
'new'.
> 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)
