[
https://issues.apache.org/jira/browse/HADOOP-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600639#action_12600639
]
Steve Loughran commented on HADOOP-3448:
----------------------------------------
The problem has 'gone away'; I think forcing clean builds through fixed it.
Given I was running the same version everywhere, I was somewhat surprised too.
two possible causes
-classloader/dual version on path (ivy is in charge of CP setup; it should
have caught this)
-cached versions of constants not being picked up
Although Java is fairly smart with dependencies, constant primitive types get
copied around at compile time, so can be out of date if something changes.
anyway, the build is fixed. Should the patch be needed? Well, maybe the text
could be clearer or just point to a wiki page discussing this issue.
> 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.
