[
https://issues.apache.org/jira/browse/HBASE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609926#comment-13609926
]
ramkrishna.s.vasudevan commented on HBASE-5583:
-----------------------------------------------
But going with seperate node we have to do the bookkeeping work for that new
node.
Also need to take care of exception that come out on setting data on that
znode.
Advantage that we get by updating the same table znode is that things are easy
to maintain and we can do the updates automically like the deletion/updation of
the table node alone would suffice to indicate some operation is done. But
when we have another znode we need to update that znode also and things will
not be automic.
Particularly on restart scenarios we may face some problems. Anyway will list
out the probs that i faced with one and 2 znodes.
> 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.95.0
>
> Attachments: HBASE-5583_new_1.patch
>
>
> -> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
