hbase-dev mailing list archives

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

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

stack commented on HBASE-743:
-----------------------------

Sebastien, what with Izaak's documentation above and my change to the message that comes out
of the migration when logs are present, is that sufficient to close this issue?

Here is the message that comes out of the migration when redo logs are present:

{code}
    if (unrecoveredLogs.size() != 0) {
      throw new IOException("There are " + unrecoveredLogs.size() +
          " unrecovered region server logs. Please uninstall this version of " +
          "HBase, re-install the previous version, start your cluster and " +
          "shut it down cleanly, so that all region server logs are recovered" +
          " and deleted.  Or, if you are sure logs are vestige of old " +
          "failures in hbase, remove them and then rerun the migration.  " +
          "See 'Redo Logs' in http://wiki.apache.org/hadoop/Hbase/HowToMigrate. " +
          "Here are the problem log files: " + unrecoveredLogs);
    } 
{code}

> 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