[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214963#comment-15214963
]
stack commented on HBASE-15549:
-------------------------------
bq. How is this different from hbase.balancer.tablesOnMaster ? Seems weird to
have to configs that do the same thing.
Thanks. [~mbertozzi] pointed out same thing. tablesOnMaster is kinda wonky. You
pass 'none' to have no tables on master (As Matteo notes, you better not name
your table 'none'). If you pass nothing, you get 'tables on master' (I passed
'false' because I misread that its supposed to be a list of Strings and got
extra confused because it 'worked'). Matteo also notes for this to work all
needs to subclass the base load balancer... not all balancers do.
Will do another version of patch.
Wanted to get an issue in to start catching the master-is-a-regionserver flak
too.
> Undo HMaster carrying regions in master branch as default
> ---------------------------------------------------------
>
> Key: HBASE-15549
> URL: https://issues.apache.org/jira/browse/HBASE-15549
> Project: HBase
> Issue Type: Bug
> Components: Balancer, master
> Reporter: stack
> Attachments: 15549.patch
>
>
> I thought we had an issue to do this but I can't find it so here is a new one.
> Currently, in master branch, HMaster is a RegionServer and carries meta
> regions such as hbase:meta. Disable this facility by default until better
> thought through (I think we should undo master ever carrying regions; FBers
> are thinking we should go forward with notion that master carries meta/system
> regions. TODO). I want to disable it because this facility is not finished
> and meantime I want to test new stuff coming in on master branch w/o this new
> feature getting in the way.
> Parking here a patch that has how to disable master carrying regions and a
> probably redundant test that ensures all works when master is not carrying
> meta regions (added because it WASN'T working for me -- but was pilot error).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
