[
https://issues.apache.org/jira/browse/HBASE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614690#action_12614690
]
Sebastien Rainville commented on HBASE-743:
-------------------------------------------
Here's how I reproduce the problem:
(in hbase-0.1.3)
rm -Rf $HBASE_DATA_DIR
bin/start-hbase.sh
ls $HBASE_DATA_DIR => a redo log exists
bin/stop-hbase.sh
ls $HBASE_DATA_DIR => the redo log is not there anymore: so far so good
bin/start-hbase.sh
ls $HBASE_DATA_DIR => a redo log exists
kill -9 $HBASE_MASTER_PID
ls $HBASE_DATA_DIR => a redo log still exists
bin/start-hbase.sh
ls $HBASE_DATA_DIR => now there are 2 redo logs
bin/stop-hbase.sh
ls $HBASE_DATA_DIR => now there is only 1 redo log: the bad one
(in hbase-trunk)
bin/hbase migrate upgrade => FAIL because of an unrecovered redo log
Now, I don't know how that's supposed to be handled but the thing is that HBase
wasn't always very *stable* so remaining redo logs like that are likely to
exist for other people so it's going to come up again.
> 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.
