You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2009/02/11 19:34:59 UTC

[jira] Commented: (HBASE-1195) If HBase directory exists but version file is inexistent, still proceed with bootstrapping

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

Jim Kellerman commented on HBASE-1195:
--------------------------------------

This is probably safe to do now. 

In the (very early) days, there was no version file, so that signaled a need to upgrade to the first release that had a version file.

Since we've had them ever since, shouldn't be a problem unless root or meta regions already exist.

> If HBase directory exists but version file is inexistent, still proceed with bootstrapping
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1195
>                 URL: https://issues.apache.org/jira/browse/HBASE-1195
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: master
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.20.0
>
>
> On the dev list I suggested we change the way we manage the empty HBase directory case. Stack answered:
> {quote}
> Yes. In fact, its probably safe-to-do now we've left far behind the
> pre-history versions of hbase where there was no hbase.version file in the
> hbase.rootdir.  If absent, lets proceed and just write it rather than treat
> it as a non-migrated instance
> {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.