[
https://issues.apache.org/jira/browse/HBASE-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115104#comment-16115104
]
Zach York commented on HBASE-18511:
-----------------------------------
Why do we need to add an additional conf value? We already have
hbase.balancer.tablesOnMaster. It seems like to accomplish this same
functionality, all you need to do is pass 'none' as the default in the
conf.get(). If we want to maintain the ability to put the current default
tables on master without having to specify all of them, we could have that
option be 'default_tables' or 'system_tables' or something like that. Also,
since there will no longer be any 'default' tables on master, you should
probably change the name of DEFAULT_TABLES_ON_MASTER.
P.S. This would be a good thing to call out in any migration doc.
> 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
