hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2668) [hbase] Documentation and improved logging so fact that hbase now requires migration comes as less of a surprise
Date Sun, 20 Jan 2008 01:50:34 GMT

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

stack updated HADOOP-2668:
--------------------------

    Summary: [hbase] Documentation and improved logging so fact that hbase now requires migration
comes as less of a surprise  (was: [hbase] After 2643, cluster won't start if FS was created
by an older hbase version)

I should have said, in spite of the exception, I did not get that I was supposed to run the
migration.  The thing just looks broke.  My guess is that users will think the same.

Agreed, to move past r613469, running migration is needed and yes, lets make this issue be
about making the migration easier to find and run -- add to bin/hbase -- and about documentation
('Getting Started' doc., incompatible changes in the release notes, IRC, etc.).

Would help if there was a prefatory message that script is verifying the cluster is down.

> [hbase] Documentation and improved logging so fact that hbase now requires migration
comes as less of a surprise
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2668
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2668
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: migrate.patch
>
>
> Hbase now checks for a version file.  If none, it reports a version mismatch.  There
will be no version file if the hbase was made by a version older than r613469

-- 
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