[
https://issues.apache.org/jira/browse/HBASE-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604680#comment-13604680
]
Matteo Bertozzi commented on HBASE-8131:
----------------------------------------
Not sure about the current lock implementation.
In my idea, the lock should also be used on master restart to rollback a table
{code}
createTable()
table Lock
...handleCreateTable...
-----> Exception <---
table Unlock
{code}
if you have an exception on table creation you should remove the assignment
manger znode, but you should also remove the data from disk and .META.
NOTE that it may be a hdfs problem (network error or similar), in this case the
master may shutdown. In this case on startup you should check the table lock
and rollback the operation (because if the error was caused by hdfs, you can't
even remove stuff.. same for zk)
> Create table handler needs to handle failure cases.
> ---------------------------------------------------
>
> Key: HBASE-8131
> URL: https://issues.apache.org/jira/browse/HBASE-8131
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.98.0
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: HBASE-8131_trunk.patch
>
>
> In CreateTable Handler there are number of failure cases.
> IOExceptions are common while creation of regioninfos, htableDescriptors etc.
> After this exception if i try to recreate the table using admin, we need to
> remove the acquired table lock and also clear the ZKTable in memory cache so
> that the operation can be retried.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
