[
https://issues.apache.org/jira/browse/HBASE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620654#comment-13620654
]
Enis Soztutar commented on HBASE-5583:
--------------------------------------
Thanks Ram. Yes, the design in HBASE-5487 is not finalized yet unfortunately.
We wanted to bring FATE, which will only handle the client initiated
operations, not stuff like region assignment. Then the other WAL approaches
came, and now Sergey's design. In any case, the issue probably won't cut it for
0.94.
I would not object to getting the patch in this issue in, given that the design
is still in discussion. My only concern would be that the table state is
checked in a lot of places, so we should be careful. If you think that solving
this issue only for create table with splits is important we can go with your
approach. Otherwise, I would wait for a resolution on HBASE-5487.
> 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, HBASE-5583_new_1_review.patch,
> HBASE-5583_new_2.patch, HBASE-5583_new_4_WIP.patch,
> HBASE-5583_new_5_WIP_using_tableznode.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
