[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214956#comment-15214956
]
stack commented on HBASE-15549:
-------------------------------
bq. What's not finished?
What Master's personality is going forward. What we have now is just wrong with
master carrying regions but only some regions and then the ones it does carry
are the critical ones. Master is now inline with writes. This sort of deploy
won't scale (one server only carrying metadata), etc.
I'm game for entertaining Master being a RegionServer or Master not being a
RegionServer but this half-baked notion where Master is sort of a RegionServer.
Testing, ITBLL doesn't work for me. Trying to figure why. Want to be able to
undo this behavior.
> 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)
