stack commented on HBASE-18511:

.006 should fix most of the test failures.

Its not finished yet though. I've put in place a boolean flag for tables on 
master, yes or no. I need to add tests for case where flag is true (currently 
it is false).  There is then the case where systems tables were exclusively on 
master. That will be another flag rather than a table list. I need to do that 
too. Working on it.

> 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, 
> HBASE-18511.master.004.patch, HBASE-18511.master.005.patch, 
> HBASE-18511.master.006.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

Reply via email to