hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10569) Co-locate meta and master
Date Wed, 14 May 2014 02:50:18 GMT

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

Enis Soztutar commented on HBASE-10569:

bq. 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).
I though unless we break it, it should be de facto from release to release. Opened HBASE-11164.

bq. At hackathon discussion was a means of maintaining the current topology – i.e. Masters
do mastering and nothing else, BU Masters sit idle
This is why I was arguing that backup masters should default to hosting no regions unless
explicitly specified. 
bq. 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.
Agreed, that is what we are going to do. 
bq. 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.
My concern is that if we cannot immediately get the benefits of co-locating, and the vendors
or some big deployments won't turn this on, what is the benefit of having this complexity.
We should not do this for saving on RPC's, but actually getting rid of master in-memory state.
If we have the state in meta and only in meta, then we won't need colocation requirements
or meta-as-a-single-region. 

> 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