[jira] [Commented] (HBASE-5583) Master restart on create table with splitkeys does not recreate table with all the splitkey regions

["Jonathan Hsieh (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233150#comment-13233150 ] 

Jonathan Hsieh commented on HBASE-5583:
---------------------------------------

Maybe we should put plans for master actions into ZK, and then remove each step as they are completed.  This would allow a backup master or the restarted master to pick up and continue where the previous master had died.

So this we may have a zk structure act like a queue with region infos and then let the masters drain from there to create .META. rows.

I was thinking about adding a flag to info:regioninfo or extra column ("info:unfinshedPresplitCreate") but this would seem to suffer from a similar problem if the master failed as these were being removed after all regions created.
                
> Master restart on create table with splitkeys does not recreate table with all the splitkey regions
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5583
>                 URL: https://issues.apache.org/jira/browse/HBASE-5583
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.96.0
>
>
> -> Create table using splitkeys
> -> MAster goes down before all regions are added to meta
> -> On master restart the table is again enabled but with less number of regions than specified in splitkeys
> Anyway client will get an exception if i had called sync create table.  But table exists or not check will say table exists. 
> Is this scenario to be handled by client only or can we have some mechanism on the master side for this? Pls suggest.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira