[
https://issues.apache.org/jira/browse/HBASE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614779#action_12614779
]
irubin edited comment on HBASE-743 at 7/18/08 3:08 PM:
------------------------------------------------------------
I see, that makes sense. I'm not sure that this is necessarily a problem with
the migrate command, although I suppose it could be a bit more tolerant. I'll
ask Jim or Stack about this.
Still, I think the right thing to do would be to just warn people about this
before they migrate, and show them how to remove any stray redo logs. I'll
make a note of this on the wiki page.
was (Author: irubin):
I see, that makes sense. I'm not sure that this is necessarily a problem
with the migrate command, although I suppose it could be a bit more tolerant.
I'll ask Jim or Stack about this.
Still, I think the right thing to do would be to just warn people about this
before they migrate, and point them to the directory where any redo logs might
be hanging around. I'll make a note of this on the wiki page.
> 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.
