[
https://issues.apache.org/jira/browse/HBASE-21866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770345#comment-16770345
]
Xu Cang commented on HBASE-21866:
---------------------------------
[~nihaljain.cs]
>From my understanding, if the line you mentioned is reached, it means
{code:java}
if (MetaTableAccessor.tableExists(env.getMasterServices().getConnection(),
tableName))
{code}
returns false, table wasn't exist before. So, we are not facing the problem.
Let me know if I misunderstood you. Thanks
> Do not move the table to null rsgroup when creating an existing table
> ---------------------------------------------------------------------
>
> Key: HBASE-21866
> URL: https://issues.apache.org/jira/browse/HBASE-21866
> Project: HBase
> Issue Type: Bug
> Components: proc-v2, rsgroup
> Reporter: Xiang Li
> Assignee: Xiang Li
> Priority: Major
> Attachments: HBASE-21866.branch-1.000.patch,
> HBASE-21866.master.000.patch, HBASE-21866.master.001.patch,
> HBASE-21866.master.002.patch, HBASE-21866.master.003.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 and instead, we should keep t1 as where it originally
> is.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
