[
https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949729#comment-13949729
]
Jimmy Xiang commented on HBASE-10569:
-------------------------------------
bq. So when we failover the master we'll force a move of meta. Won't that lead
to bigger "blib" than before.
Namespace and ACL are small tables cached in ZK/RS. For META, yes, it's a
bigger "blib". If we remove ZK from the assignment in the future, when the
master is failing over, nobody can update the meta. In this case, the meta info
cached in the client side won't change.
bq. Seems like this will wreak havoc to data locality.
In HBASE-10815, we will introduce a configuration so that we can exclude backup
masters from serving regions. That should help.
> 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)
