Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 15 Aug 2017 10:36:00 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13092077.1501739239000.32687.1502793360929@Atlassian.JIRA>
In-Reply-To: <JIRA.13092077.1501739239000@Atlassian.JIRA>
References: <JIRA.13092077.1501739239000@Atlassian.JIRA> <JIRA.13092077.1501739239476@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-18511) Default no regions on master
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 15 Aug 2017 10:36:11 -0000


     [ https://issues.apache.org/jira/browse/HBASE-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-18511:
--------------------------------
    Release Note: 
Changes the configuration hbase.balancer.tablesOnMaster from list of table names that the can carry (with 'none' meaning no tables on the master) to instead be a boolean that is set to true if master carries tables/regions and false if it does not. If true, the master acts like any regionserver.

If false, then the master carries no tables. This is the default for hbase-2.0.0.

Another boolean configuration, hbase.balancer.tablesOnMaster.systemTablesOnly, when set to true, enables hbase.balancer.tablesOnMaster and makes it so the master hosts system tables exclusively (the long-time deploy mode of master branch and branch-2 up until this commit).

The change of hbase.balancer.tablesOnMaster from String list to boolean and
the addition of a simple boolean to enable system-tables on Master was done
to constrain what operators might ask for via this master configuration.
Stipulating what tables are bound to the Master server verges into
regionserver grouping territory, a more robust means of specifying table
and server combinations. Operators should use this latter if they want
layouts more exotic than those supplied by the provided booleans.

  was:
Changes the configuration hbase.balancer.tablesOnMaster from list of table names that the can carry (with 'none' meaning no tables on the master) to instead be a boolean that is set to true if master carries tables/regions and false if it does not. If true, the master acts like any regionserver.

If false, then the master carries no tables. This is the default for hbase-2.0.0.

Another boolean configuration, hbase.balancer.tablesOnMaster.systemTablesOnly, when set to true, enables hbase.balancer.tablesOnMaster and makes it so the master hosts system tables exclusively (the long-time deploy mode of master branch and branch-2 up until this commit). 


> 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, HBASE-18511.master.007.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)