hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Au (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5203) TT's version build is too restrictive
Date Tue, 07 Apr 2009 18:40:13 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bill Au updated HADOOP-5203:
----------------------------

    Attachment: HADOOP-5203-md5-0.18.3.patch

I back ported Rick's patch to 0.18.3.  I have tested it in my cluster which include 5 different
hardware/OS combination.  All the different TaskTracker was able to come up without any problem.
 I am attaching my patch.

Also want to confirm what Rick has pointed out.  All the Datanodes have no problem talking
to the Namenode in my cluster of mixed machines.

> TT's version build is too restrictive
> -------------------------------------
>
>                 Key: HADOOP-5203
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5203
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Runping Qi
>            Assignee: Rick Cox
>         Attachments: HADOOP-5203-md5-0.18.3.patch, HADOOP-5203-md5.patch, HADOOP-5203.patch
>
>
> At start time, TT checks whether its version is compatible with JT.
> The condition is too restrictive. 
> It will shut down itself if one of the following conditions fail:
> * the version numbers must match
> * the revision numbers must match
> * the user ids who build the jar must match
> * the build times must match
> I think it should check the major part of the version numbers only (thus any version
like 0.19.xxxx should be compatible).

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