hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Izaak Rubin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-743) bin/hbase migrate upgrade fails when redo logs exists
Date Fri, 18 Jul 2008 23:01:31 GMT

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

Izaak Rubin commented on HBASE-743:
-----------------------------------

I've updated the HBase Wiki page on migrations, mentioning the issue of unrecovered redo logs:

http://wiki.apache.org/hadoop/Hbase/HowToMigrate

I'm not sure if there's a way for HBase to go through and merge-in these redo logs - if so,
I'll post it to the migration page as well.  If something like this doesn't exist, it might
be a good idea to make it.

> bin/hbase migrate upgrade fails when redo logs exists
> -----------------------------------------------------
>
>                 Key: HBASE-743
>                 URL: https://issues.apache.org/jira/browse/HBASE-743
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Sebastien Rainville
>            Assignee: Izaak Rubin
>            Priority: Minor
>
> I migrated several hbase-0.1.3 instances to hbase trunk and even if I stop hbase-0.1.3
cleanup it leaves redo logs on hdfs. The problems is that when migrating the data with hbase-trunk
it fails because it finds these redo-logs and quit with a error message saying that we should
reinstall the old hbase and shut it down cleanly and that in theory it erases the redo logs.
The work around has been to delete the redo logs manually... which is bad.

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