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 2008/06/04 19:30:45 UTC

[jira] Updated: (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:all-tabpanel ]

Owen O'Malley updated HADOOP-3448:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.18.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Steve!

> 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
>            Assignee: Steve Loughran
>            Priority: Minor
>             Fix For: 0.18.0
>
>         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.