hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgeny Ryabitskiy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1195) If HBase directory exists but version file is inexistent, still proceed with bootstrapping
Date Thu, 23 Apr 2009 10:12:47 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Evgeny Ryabitskiy updated HBASE-1195:
-------------------------------------

    Attachment: HBASE-1195.patch

Fixed FSUtils.checkVersion(fs, rootdir, true);

Changes:
 * If root dir empty (no version file and no ROOT Region dir), just create new version file
 * But if there exists ROOT Region dir and no Version file, should be required migration.

Not changed:
 * if version not matched ask for

> 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: Evgeny Ryabitskiy
>            Priority: Minor
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1195.patch
>
>
> 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.


Mime
View raw message