[ https://issues.apache.org/jira/browse/HBASE-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588230#comment-16588230 ]
Xu Cang commented on HBASE-20666: --------------------------------- not sure why this test failed: [.org.apache.hadoop.hbase.master.assignment.TestMergeTableRegionsProcedure|https://builds.apache.org/job/PreCommit-HBASE-Build/14123/testReport/org.apache.hadoop.hbase.master.assignment/TestMergeTableRegionsProcedure/org_apache_hadoop_hbase_master_assignment_TestMergeTableRegionsProcedure/] I ran it locally, it ran without any error. > Unsuccessful table creation leaves entry in hbase:rsgroup table > --------------------------------------------------------------- > > Key: HBASE-20666 > URL: https://issues.apache.org/jira/browse/HBASE-20666 > Project: HBase > Issue Type: Bug > Reporter: Biju Nair > Assignee: Xu Cang > Priority: Minor > Attachments: HBASE-20666.master.001.patch, > HBASE-20666.master.002.patch, HBASE-20666.master.004.patch > > > If a table creation fails in a cluster enabled with {{rsgroup}} feature, the > table is still listed as part of {{default}} rsgroup. > To recreate the scenario: > - Create a namespace (NS) with number of region limit > - Create table in the NS which satisfies the region limit by pre-splitting > - Create a new table in the NS which will fail > - {{list_rsgroup}} will show the table being part of {{default}} rsgroup and > data can be found in {{hbase:rsgroup}} table > Would be good to revert the entry when the table creation fails or a script > to clean up the metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)