[
https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996691#comment-13996691
]
Matteo Bertozzi commented on HBASE-10569:
-----------------------------------------
I think the main motivation is the colocation of all the components that are
usually involved in a single "transaction". The main example of this is the
Assignment, which involve: Master, META, ZooKeeper.
#1 and #2 are part of a generic notification system, which will be used to
propagate ACLs, Visibility, Quotas. (In theory the base of this system is also
the one behind the ZK-less Assignment)
For the Horizontal scalability, I think that we are going to have Multiple
Master each one operating on its subsection of "meta" (and the notification
system). This means that you will have concurrent assignments on different
masters.
The best case is where you can fit a full table (regions metadata) on a single
master, the other case is where your table is split on multiple master which
means that operation that requires to work on the full set of regions e.g.
delete, disable, enable need some sort of coordination to provide the full
consistency that you'll get with a full table that fits on a single master.
> 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: Co-locateMetaAndMasterHBASE-10569.pdf,
> hbase-10569_v1.patch, hbase-10569_v2.patch, hbase-10569_v3.1.patch,
> hbase-10569_v3.patch, master_rs.pdf
>
>
> 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)
