[
https://issues.apache.org/jira/browse/HADOOP-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674871#action_12674871
]
Rick Cox commented on HADOOP-5203:
----------------------------------
Does "only takstrackers and jobtrackers built from exactly the same source
files should communicate" accurately describe the desired policy?
If so, I can try to provide a patch for saveVersions.sh that will md5sum the
entire source and use that in the version identifier, as an alternative way to
enforce that policy. A single character source-level change would be declared
incompatible, but rebuilding from exactly the same source would be OK.
> 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
> 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.
