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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2008/05/27 18:30:07 UTC
[jira] Commented: (HADOOP-3448) Add some more hints of the problem
when datanode and namenode don't match
[ https://issues.apache.org/jira/browse/HADOOP-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600182#action_12600182 ]
Steve Loughran commented on HADOOP-3448:
----------------------------------------
The patch I've submitted adds the version information, so the the stack trace can be more useful than :
java.lang.AssertionError: Data-node and name-node layout versions must be the same.,
However, one thing to consider is whether this should be checked every time the datanode starts up, rather than skipping it if -ea is disabled. Otherwise there is a risk that the problem will not be picked up in production.
> 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: documentation
> 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.