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 Mon, 14 Jul 2008 23:10:32 GMT

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

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

Hi Sebastien,

I'm having difficulty replicating the problem on my machine. I don't totally understand what
you mean by the hbase-0.1.3 cleanup, but I'll explain what I did and you can tell me if I
did something different. I started a version of hbase-0.1.3 running on top of hadoop-0.16.4,
created a table with a bunch of data, shut down hbase, and then upgraded my hadoop from 0.16.4
to 0.17.1. I followed the hadoop upgrading instructions at http://wiki.apache.org/hadoop/Hadoop%20Upgrade.
Then I went to my hbase-trunk and ran:
{code}
./bin/hbase migrate update
{code}
Which ran successfully. I then started up hbase-trunk and the table i had created looked unchanged.

It's true that the migrate script will fail if it sees these stray log files in the dfs. Shutting
down hbase normally should clean up these log files... This is where I'm a bit confused about
what you mean by "hbase-0.1.3 cleanup," and that even if you do stop it it'll leave redo-logs?
Wouldn't it be that if you didn't stop the cleanup it leaves redo-logs? (Since the cleanup
should get rid of the redo logs?)

> 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