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 Wed, 14 May 2014 00:53:22 GMT

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

stack commented on HBASE-10569:


bq. Will this break rolling upgrades from 0.98 -> 0.99? We want to keep 0.98 to 1.0 rolling
restart support. 

It is required we can rolling upgrade from 0.98 to 1.0 (do we have that in our 1.0 scope doc?
 If not, lets do so).  This feature should not preclude.  At hackathon discussion was a means
of maintaining the current topology -- i.e. Masters do mastering and nothing else, BU Masters
sit idle -- because at least for vendors who are not at a major version juncture when hbase
1.0 ships, they'll probably want to keep the old layout.  I think that as long as we can do
a rolling upgrade and we broadcast it loud enough in the release notes, a master's role changing
going from 0.98 to 0.99 such that it hosts regions would be fine (in apache hbase).

bq. if we are also allowing to completely disable this feature (as in the other jira), will
there still be benefit for this?

I think it on by default in 1.0 apache hbase.  If not then, if others think differently, on
by default in apache hbase 2.0.

I updated the attached doc. to address some of the comments.  I also put there as something
to keep in mind Francis's requirement that hbase master be able to do 1M regions (host and
assign fast) very soon and 50M regions not too long after that.

> 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: stack
>             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