hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8968) TaskTracker and DataNode relaxed version check is not working
Date Wed, 24 Oct 2012 21:40:14 GMT

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

Alejandro Abdelnur commented on HADOOP-8968:

Eli, thanks for the review.

Regarding the exact version mach on relaxed check, if a patch release (ie is done
then the current logic will not allow the TT to start. With the proposed patch, it would work.
And giving flexibility, it would allow to change the precision.

Regarding backporting VersionUtil (I assume you meant that) from HDFS-2983, I've looked at
it first, but the compareVersions() method compares the whole version string, there is not
way to define the precision.

Regarding 'Either way..', the current patch does it for both MR and HDFS.

Said this, I'd be OK with a full version disabling as well. I was just trying to constraint
versions a bit.
> 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

View raw message