[
https://issues.apache.org/jira/browse/HBASE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976006#comment-13976006
]
Enis Soztutar commented on HBASE-10873:
---------------------------------------
bq. Sounds like you'd like us to replicate the old deploy layout Enis Soztutar
but with option to move to the 'new'.
Yes. Least amount of surprises. Since we are right now defaulting to master
having no user level regions, we should also default to backup masters not
having any user level regions.
It may be ok to change the defaults so that both active and backup masters have
normal region load (weight 1), but I think we should be consistent for region
loads of active and backup masters. Since META is already shared in 0.98-
setups, it should be fine to have master be just another region server. In that
case, we do not even need this issue?
> 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)
