[
https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997854#comment-13997854
]
Jonathan Hsieh commented on HBASE-10569:
----------------------------------------
I thought that is what we agreed upon old topology default for 1.0 and new
topology default for trunk/2.0 during the pow-wow.
My vote is to keep the old topology for hbase 1.0, but have the option to go
new in 1.0. For 2.0/trunk, we default to the new topology. The old topology
is well understood operationally for deploys. Though straightforward for us
devs, I think having a brand new deployment style with gotcha's we haven't
figured out at scale with yet is risky for what we want to be a super stable
release.
> 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)
