hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10569) Co-locate meta and master
Date Fri, 16 May 2014 21:28:21 GMT

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

Mikhail Antonov commented on HBASE-10569:
-----------------------------------------

Regarding some discussion about hosting META on master

 - if we want to run cluster with 1M or 50M regions (HBASE-11165), we may (will?) have to
host META regions on multiple servers
 - on the zk-less assignments (HBASE-11059), short-circuit atomic updates of meta were mentioned
(making use of the fact that meta is local to master).

That said, how do we now define that - is hosting meta on master the very-nice-to-have optimization,
or is that pre-requisite for cluster to function?



> 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)

Mime
View raw message