Details

    • Type: Task
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: master
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change
    • Release Note:
      Hide
      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).

      UPDATE: This is broke. See HBASE-19785.
      UPDATE2: Master carrying Regions does not work reliably, see HBASE-19828.

      See HBASE-19831, the issue to fix regions on Master

      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.
      Show
      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). UPDATE: This is broke. See HBASE-19785 . UPDATE2: Master carrying Regions does not work reliably, see HBASE-19828 . See HBASE-19831 , the issue to fix regions on Master 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.

      Description

      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).

        Attachments

        1. HBASE-18511.master.001.patch
          2 kB
          stack
        2. HBASE-18511.master.002.patch
          22 kB
          stack
        3. HBASE-18511.master.003.patch
          22 kB
          stack
        4. HBASE-18511.master.004.patch
          39 kB
          stack
        5. HBASE-18511.master.005.patch
          39 kB
          stack
        6. HBASE-18511.master.006.patch
          56 kB
          stack
        7. HBASE-18511.master.007.patch
          76 kB
          stack
        8. HBASE-18511.master.008.patch
          78 kB
          stack
        9. HBASE-18511.master.009.patch
          80 kB
          stack
        10. HBASE-18511.master.010.patch
          81 kB
          stack
        11. HBASE-18511.master.011.patch
          82 kB
          stack
        12. HBASE-18511.master.012.patch
          82 kB
          stack
        13. HBASE-18511.master.013.patch
          82 kB
          stack
        14. HBASE-18511.master.014.patch
          82 kB
          stack
        15. HBASE-18511.master.015.patch
          82 kB
          stack

          Issue Links

            Activity

              People

              • Assignee:
                stack stack
                Reporter:
                stack stack
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: