[HBASE-17350] Fixup of regionserver group-based assignment

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: regionserver, rsgroup
• Hadoop Flags: Reviewed

Release Note

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.

• Assignee: Michael Stack
• Reporter: Michael Stack
• Created: 20/Dec/16 16:09
• Updated: 01/Jul/22 20:54
• Resolved: 06/Feb/17 21:13

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.

Issue Links

• is related to: HBASE-15631 Backport Regionserver Groups (HBASE-6721) to branch-1
• links to: Review Board (master)