Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: regionserver, rsgroup
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      A few bug fixes and tweaks to the fsgroup feature.

      Renamed shell command move_rsgroup_servers as move_servers_rsgroup
      Renamed shell comand move_rsgroup_tables as move_tables_rsgroup

      Made the 'default' group more 'dynamic'; i.e. dead servers no longer show in the 'default' group.
      Show
      A few bug fixes and tweaks to the fsgroup feature. Renamed shell command move_rsgroup_servers as move_servers_rsgroup Renamed shell comand move_rsgroup_tables as move_tables_rsgroup Made the 'default' group more 'dynamic'; i.e. dead servers no longer show in the 'default' group.

      Description

      Can we do some fixup on the regionserver group-based assignement before it makes it into a release? Here are a few items after trying to use it last night:

      + The commands are named inconsistently. Usually it is verb with a rsgroup suffix but we have get_table_rsgroups and then move_rsgoup_tables. Ditto for servers.
      + In local mode, the regionserver doesn't belong to a group. Shouldn't it?
      + Adding a server to a group with the move_rsgroup_tables is non-intuitive, to me at least (especially given #2 above).
      + The error message you get when you run one of these rsgroup commands should tell you how to set up rsgroups rather than dump out a cryptic exception.

      Thats all for now.

        Attachments

        1. HBASE-17350.master.005.patch
          50 kB
          stack
        2. HBASE-17350.master.004.patch
          46 kB
          stack
        3. HBASE-17350.master.003.patch
          46 kB
          stack
        4. HBASE-17350.master.002.patch
          45 kB
          stack
        5. HBASE-17350.master.001.patch
          17 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: