[
https://issues.apache.org/jira/browse/HBASE-13815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566167#comment-14566167
]
Stephen Yuan Jiang commented on HBASE-13815:
--------------------------------------------
[~mbertozzi] I think the fix is to move the
{{env.getMasterServices().getAssignmentManager().getTableStateManager().setDeletedTable(tableName);}}
statement from {{deleteAssignmentState}} method to the {{deleteTableStates}}
method in DeleteTableProcedure. This would solve the problem.
> Procedure V2: Rollback of CreateTableProcedure should clear the table state
> ---------------------------------------------------------------------------
>
> Key: HBASE-13815
> URL: https://issues.apache.org/jira/browse/HBASE-13815
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Stephen Yuan Jiang
> Assignee: Stephen Yuan Jiang
>
> If CreateTableProcedure rolls back, depending on the steps of the procedure,
> it might not change the table state to be 'Deleted' or just delete the table
> state.
> In branch-1 and its child branches, the following exception will throw if the
> table is created again and the previous rollback is not clean:
> {noformat}
> 2015-05-30 06:30:05,287 WARN [ProcedureExecutorThread-1]
> procedure.CreateTableProcedure: The table xyz does not exist in meta but has
> a znode. run hbck to fix inconsistencies.
> {noformat}
> In master branch, the table state is not checked during
> CreateTableProcedure#prepareCreate(), but we still need to make sure that the
> table state is in a consistent state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
