hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3448) Add some more hints of the problem when datanode and namenode don't match
Date Thu, 29 May 2008 08:34:45 GMT

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

Steve Loughran commented on HADOOP-3448:
----------------------------------------

Its probably because the .class files dont even track where constants came from. Change a
constant: do a clean build. 

Perhaps we should change the assert to say this. 

> Add some more hints of the problem when datanode and namenode don't match
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-3448
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3448
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.18.0
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: hadoop-3448.patch
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> When there is a mismatch between name and data mode, and you are running with -ea set,
then Datanode.handshake() bails out with an assertion  "Data-node and name-node layout versions
must be the same.";
> However, this message doesnt actually say which version numbers are at fault. A better
error message would include the version information, so pointing the finger of blame would
be easier.

-- 
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