[
https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949612#comment-13949612
]
Lars Hofhansl commented on HBASE-10569:
---------------------------------------
Just noticed this issue now.
bq. Active master serves table META, namespace, and ACL in a secure
installation.
So when we failover the master we'll force a move of meta. Won't that lead to
bigger "blib" than before.
bq. Backup masters are regionservers too. They serve regions, while trying to
be the next active master. Once a backup master becomes the active one, it will
serve META and namespace table. Load balancer will move user regions to other
regionservers.
Seems like this will wreak havoc to data locality.
Master failover used to be a light weight event. I fear this makes it much more
heavy weight.
> Co-locate meta and master
> -------------------------
>
> Key: HBASE-10569
> URL: https://issues.apache.org/jira/browse/HBASE-10569
> Project: HBase
> Issue Type: Improvement
> Components: master, Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.99.0
>
> Attachments: hbase-10569_v1.patch, hbase-10569_v2.patch,
> hbase-10569_v3.1.patch, hbase-10569_v3.patch
>
>
> I was thinking simplifying/improving the region assignments. The first step
> is to co-locate the meta and the master as many people agreed on HBASE-5487.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
