[ https://issues.apache.org/jira/browse/HBASE-21866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767241#comment-16767241 ]
Xiang Li commented on HBASE-21866: ---------------------------------- [~xucang] Thanks for your guide! Uploaded the very first patch (v000) to demonstrate the idea! I did not update the logic in isRollbackSupported() but surrounding your change in HBASE-20666 as well as "DeleteTableProcedure.deleteTableStates(env, getTableName());" into a "if" clause, to make those actions only be taken when the rollback of TableCreateProcedure is not due to TableExistsException. Make any sense to you? > Do not move the table to null rsgroup when creating a existing table > -------------------------------------------------------------------- > > Key: HBASE-21866 > URL: https://issues.apache.org/jira/browse/HBASE-21866 > Project: HBase > Issue Type: Bug > Components: rsgroup > Reporter: Xiang Li > Assignee: Xiang Li > Priority: Major > Attachments: HBASE-21866.master.000.patch > > > By using the latest HBase master branch, the bug could be re-produced as: > # create 't1', 'cf1' > # create 't1', 'cf1' > The following message is logged into HMaster's log: > {code} > INFO [PEWorker-12] rsgroup.RSGroupAdminServer: Moving table t1 to RSGroup > null > {code} > This is a wrong action that we should keep t1 as where it originally is. -- This message was sent by Atlassian JIRA (v7.6.3#76005)