Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1839007659.1216676853388.JavaMail.jira@brutus>
Date: Mon, 21 Jul 2008 14:47:33 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-743) bin/hbase migrate upgrade fails when
 redo logs exists
In-Reply-To: <571076423.1215799591644.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-743.
-------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0

Resolving (with Sebastien's OK)

> 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
>             Fix For: 0.2.0
>
>
> 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.