[ https://issues.apache.org/jira/browse/HBASE-17350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-17350: -------------------------- Resolution: Fixed 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. Status: Resolved (was: Patch Available) Pushed ot master. Thanks for reviews [~toffer] and [~elserj] > Fixup of regionserver group-based assignment > -------------------------------------------- > > Key: HBASE-17350 > URL: https://issues.apache.org/jira/browse/HBASE-17350 > Project: HBase > Issue Type: Sub-task > Components: regionserver, rsgroup > Reporter: stack > Assignee: stack > Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-17350.master.001.patch, > HBASE-17350.master.002.patch, HBASE-17350.master.003.patch, > HBASE-17350.master.004.patch, HBASE-17350.master.005.patch > > > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)