[
https://issues.apache.org/jira/browse/HADOOP-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593981#action_12593981
]
Hadoop QA commented on HADOOP-3337:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12381344/3337_20080502b.patch
against trunk revision 645773.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac -1. The applied patch generated 462 javac compiler warnings (more
than the trunk's current 458 warnings).
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2371/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2371/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2371/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2371/console
This message is automatically generated.
> Name-node fails to start because DatanodeInfo format changed.
> -------------------------------------------------------------
>
> Key: HADOOP-3337
> URL: https://issues.apache.org/jira/browse/HADOOP-3337
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Konstantin Shvachko
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: 3337_20080501.patch, 3337_20080501b.patch,
> 3337_20080502.patch, 3337_20080502b.patch
>
>
> HADOOP-3283 introduced a new field ipcPort in DatanodeInfo, which was not
> reflected in the reading/writing file system image files.
> Particularly, reading edits generated by the previous version of hadoop
> throws the following exception:
> {code}
> 08/05/02 00:02:50 ERROR dfs.NameNode: java.lang.IllegalArgumentException: No
> enum const class org.apache.hadoop.dfs.DatanodeInfo$AdminStates.0?
> /56.313
> at java.lang.Enum.valueOf(Enum.java:192)
> at org.apache.hadoop.io.WritableUtils.readEnum(WritableUtils.java:399)
> at org.apache.hadoop.dfs.DatanodeInfo.readFields(DatanodeInfo.java:318)
> at org.apache.hadoop.io.ArrayWritable.readFields(ArrayWritable.java:90)
> at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:499)
> at org.apache.hadoop.dfs.FSImage.loadFSEdits(FSImage.java:794)
> at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:664)
> at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:280)
> at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:81)
> at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:276)
> at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:257)
> at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:133)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:178)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:164)
> at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:777)
> at org.apache.hadoop.dfs.NameNode.main(NameNode.java:786)
> {code}
> and startup fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
