[
https://issues.apache.org/jira/browse/HBASE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-5583:
-----------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 2.0.0)
Status: Resolved (was: Patch Available)
This got fixed by proc-v2 HBASE-13203, where now create table and the other
DDLs are using a state machine and on restart they resume from where they left
off with all the information they need to complete the operation
> 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
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
