[
https://issues.apache.org/jira/browse/HADOOP-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483482#comment-13483482
]
Eli Collins commented on HADOOP-8968:
-------------------------------------
bq. The relaxed check is done after the strict check, thus no chance for the
relaxed check to ever happen.
The relaxed version check works, the assertion check before the relaxed version
check is not the strict check, the build version string _contains_ the version
string so we should never have the build version match w/o the version
matching, that's why this is an assert.
The relaxed version check works, it's purpose is to permit a TT to connect to a
JT with a different build version but identical version. What you want is a TT
that can connect to a JT with a different version. I'd do one of the following:
# Add a flag that disables the version check entirely
# Backport VersionInfo from HDFS-2983 rather than reimplement something similar
here
Either way I'd use the same mechanism across MR and HDFS (like HADOOP-8209).
> TaskTracker and DataNode relaxed version check is not working
> -------------------------------------------------------------
>
> Key: HADOOP-8968
> URL: https://issues.apache.org/jira/browse/HADOOP-8968
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 1.2.0
>
> Attachments: HADOOP-8968.patch
>
>
> The logic in the TaskTracker and the DataNode to allow a relax version check
> with the JobTracker and NameNode is not working.
> The relaxed check is done after the strict check, thus no chance for the
> relaxed check to ever happen.
> The relaxed check is hardcoded to require exact same versions (allowing
> different builds). The relaxed check should be able to work with a prefix of
> the full version (i.e. to handle patch releases).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
