[
https://issues.apache.org/jira/browse/HBASE-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604687#comment-13604687
]
ramkrishna.s.vasudevan commented on HBASE-8131:
-----------------------------------------------
Our comments crossed.
Ya Matteo you are right. The problem with master restart is even more bigger.
We are not sure how many regioninfos were actually needed and how many got
created. Also we are not sure if the failure happened only for making the
znode from ENABLING/ENABLED? If that was the case then it means that setting
it to ENABLED alone should be enough.
I added one api in HBaseAdmin that checks for isTableAvailable() along with the
original splitkeys that the user has passed while creating the table.
bq.you should check the table lock
For this the table lock znode should be persistent right?
> 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
