You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2012/05/08 20:51:51 UTC

[jira] [Commented] (HADOOP-8371) Hadoop 1.0.1 release - DFS rollback issues

    [ https://issues.apache.org/jira/browse/HADOOP-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270706#comment-13270706 ] 

Suresh Srinivas commented on HADOOP-8371:
-----------------------------------------

bq. Started DFS by running /usr/local/hadoop-1.0.1/bin/start-dfs.sh -rollback

When you upgrade from v1 to v2, you do it by running start-dfs.sh -upgrade on v2. After upgrade, to rollback, you have to do start-dfs.sh -rollback on * v1 * version of the software and not * v2 * as you have done here. That is the reason why you are seeing the problem.

We should still log a bug on why rollback was allowed from 1.0.1, which rolled back to namenode state from 0.20.203.
                
> Hadoop 1.0.1 release - DFS rollback issues
> ------------------------------------------
>
>                 Key: HADOOP-8371
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8371
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.0.1
>         Environment: All tests were done on a single node cluster, that runs namenode, secondarynamenode, datanode, all on one machine, running Ubuntu 12.04
>            Reporter: Giri
>            Priority: Minor
>              Labels: hdfs
>
> See the next comment for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira