hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10569) Co-locate meta and master
Date Thu, 15 May 2014 06:11:52 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998479#comment-13998479

stack commented on HBASE-10569:

bq. 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.

Point of order: If I read it right, you can only do 'agreement' on mailing list ("Community
decisions must be reached on the mailing list. " [1]).

At the powwow we raised this issue, yeah.  We said stuff like it probably more palatable,
as noted above, that "...for 1.0 we should just go w/ the old topology and do clean switch
to new layout in 2.0..." and that we needed to bring this issue to the 1.0 RM's attention.
I'd be in favor of keeping our current default for 1.0 apache hbase but would be fine if folks
want to flip the option so master carrying regions is not on by default.

1. https://blogs.apache.org/comdev/entry/how_apache_projects_use_consensus

> 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

View raw message