[jira] [Comment Edited] (HBASE-10569) Co-locate meta and master

["Jimmy Xiang (JIRA)" <ji...@apache.org>]

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

Jimmy Xiang edited comment on HBASE-10569 at 5/14/14 3:31 PM:
--------------------------------------------------------------

Totally agree with what Stack and Matteo said.

As to [~enis]'s question:

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

Big features usually come in with an option to disable it at first. This is a basic idea to introduce great features with smooth migration paths for users at the beginning, right?


was (Author: jxiang):
Totally agree with what Stack and Matteo said. 

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

Big features usually come in with an option to disable it at first. This is a basic idea to introduce great features with smooth migration paths for users at the beginning, right?

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