[
https://issues.apache.org/jira/browse/HBASE-21866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767278#comment-16767278
]
Nihal Jain commented on HBASE-21866:
------------------------------------
Can't we just move the logic of {{*postCreateTable*()}} to
{{*preCreateTableAction*()}} in *{{RSGroupAdminEndpoint}}*. (Ping [~apurtell]
since you're familiar with HBASE-19509)
If this is done, I don't think we will need to call {{*postDeleteTable*()}}
inside *{{rollback}}* of *{{CREATE_TABLE_PRE_OPERATION}}*, which seems weird in
itself since we are calling delete co-processor for a table whose creation did
not even start.
> 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)
