[
https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996641#comment-13996641
]
Francis Liu commented on HBASE-10569:
-------------------------------------
Thanks for the doc. Itd be great if we could have the list of use cases we are
trying to solve. So we have that motivate the design decisions.
During the discussion and my chat with Matteo and Jimmy here is what I got:
1. A method to guarantee security acl changes are fully propagated when a acl
change is requested
2. Same as #1 but for quota
3. Remove master daemon to simplify deployment/ops
4. Have a designated set of servers system tables will be hosted on. To isolate
it from user region workloads.
Feel free to add if I missed anything.
#3 and #4 directly motivates this patch. Tho it seeems there was an agreement
to still hqve designated hosts as masters?
It seems to me #1 and #2 are use cases for a synchronous coordination frameowrk
(consensus discussion). Which may or may not require system table colocation.
Having fault tolerant coordination as a first class primitive is sorely
missing. And I believe enable us avoid design choices which would impede
horizontal scalability.
> 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)
