[ 
https://issues.apache.org/jira/browse/HBASE-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585608#comment-16585608
 ] 

Xu Cang commented on HBASE-20666:
---------------------------------

Test result after applied patch:

 

 

 


{{hbase(main):027:0* create 'ns3:failurecase1234', 'cf2'}}{{ERROR: The table 
ns3:failurecase1234 cannot be created as it would exceed maximum number of 
tables allowed in the namespace. The total number of tables permitted is 
5}}{{For usage try 'help "create"'}}{{Took 0.2347 seconds}}
{{hbase(main):028:0> list_rsgroups}}
{{NAME SERVER / TABLE}}
{{ rsg2}}
{{ default server 192.168.0.x:16020}}
{{ table ns4:loltable5456}}
{{ table ns3:loltable3}}
{{ table ns4:loltable545678}}
{{ table ns4:successcase123}}
{{ table ns4:loltable54644445}}
{{ table hbase:meta}}
{{ table ns4:loltable54645}}
{{ table hbase:quota}}
{{ table hbase:namespace}}
{{ rsg1}}
{{3 row(s)}}
{{Took 0.0223 seconds}}
{{hbase(main):029:0>}}

> Unsuccessful table creation leaves entry in rsgroup meta 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
>
>
> 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)

Reply via email to