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 "Bill Au (JIRA)" <ji...@apache.org> on 2009/04/07 04:26:12 UTC

[jira] Commented: (HADOOP-5203) TT's version build is too restrictive

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

Bill Au commented on HADOOP-5203:
---------------------------------

What's that status of the patch for the checksum based approach?  I am using 0.18.3 and am willing to back port such a patch to 0.18.3 if necessary.  In the meantime it looks like I will have to use Doug's approach in order to get around this problem since I am using a cluster with mixed hardware and OS.

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