You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/06/04 18:46:36 UTC
[jira] Resolved: (HADOOP-1458) Upgrade from 0.13 (pre HADOOP-1242)
to 0.13 (post HADOOP-1242) does not work
[ https://issues.apache.org/jira/browse/HADOOP-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-1458.
-----------------------------------
Resolution: Won't Fix
We've agreed to just attach a fixit script here and not put it in the release.
> Upgrade from 0.13 (pre HADOOP-1242) to 0.13 (post HADOOP-1242) does not work
> ----------------------------------------------------------------------------
>
> Key: HADOOP-1458
> URL: https://issues.apache.org/jira/browse/HADOOP-1458
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.13.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.13.0
>
>
> When you convert a 0.13 NameNode storage directory from pre to post HADOOP-1242, the NameNode won't start. You'll get:
> {code}
> 07/06/04 00:10:51 ERROR dfs.NameNode: org.apache.hadoop.dfs.InconsistentFSStateException: Directory /data/hadoop/dfs/name is in an inconsistent state: /data/hadoop/dfs/name/image does not exist.
> at org.apache.hadoop.dfs.FSImage.isConversionNeeded(FSImage.java:439)
> at org.apache.hadoop.dfs.Storage$StorageDirectory.analyzeStorage(Storage.java:263)
> at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:149)
> at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:347)
> at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:251)
> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:173)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:211)
> at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:806)
> at org.apache.hadoop.dfs.NameNode.main(NameNode.java:814)
> {code}
> because the "bad" image file isn't created later in the startup. Since this is only a non-release issue, I don't know if we need to fix it programatically or can just provide an upgrade script. Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.