[
https://issues.apache.org/jira/browse/HBASE-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117935#comment-16117935
]
stack commented on HBASE-18511:
-------------------------------
Ok. Yeah, let me try this. For now boolean yes/no regions on master. If yes,
any regions. Will add new config just systems tables (currently you have to
specify the list which seems flakey and there seems to be implication you could
have master carry arbitrary tables which seems odd when we have rsgroups in the
mix... ). Working it out. Lets see what fails.
> Default no regions on master
> ----------------------------
>
> Key: HBASE-18511
> URL: https://issues.apache.org/jira/browse/HBASE-18511
> Project: HBase
> Issue Type: Task
> Components: master
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18511.master.001.patch,
> HBASE-18511.master.002.patch, HBASE-18511.master.003.patch
>
>
> Let this be umbrella issue for no-regions-on-master as default deploy (as it
> was in branch-1).
> Also need to make sure we can run WITH regions on master; in particular
> system tables with RPC short-circuit as it is now in hbase master.
> Background is that master branch carried a change that allowed Master carry
> regions. On top of this improvement on branch-1, Master defaulted to carry
> system tables only. No release was made with this configuration. Now we are
> going to cut the 2.0.0 release, the decision is that hbase-2 should have the
> same layout as hbase-1 so this issue implements the undoing of Master
> carrying system tables by default (though the capability remains).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
