[
https://issues.apache.org/jira/browse/HADOOP-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696674#action_12696674
]
Rick Cox commented on HADOOP-5203:
----------------------------------
It's a bit obfuscated, but the VersionInfo.getBuildVersion() is used by the
tasktrackers to compare versions:
TaskTracker.java:1056:
if(!VersionInfo.getBuildVersion().equals(jobTrackerBV)) {
This patch changes from including the date to including the srcChecksum in the
string returned by VersionInfo.getBuildVersion().
The namenode-datanode compatibility check uses Storage.getBuildVersion(), but
that calls VersionInfo.getRevision(), so didn't have the precise problem
addressed by this JIRA (though it might be worth changing it to match).
> 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.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.
