[
https://issues.apache.org/jira/browse/HADOOP-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485098#comment-13485098
]
Suresh Srinivas commented on HADOOP-8968:
-----------------------------------------
bq. this patch adds an option to turn off the version match completely, ie the
version string (with the embedded major, minor, point version) is ignored. V1
workers obviously can't connect to v2, and since we're not doing another major
release off branch-1 the only way you could get a DN/TT to try connect to a
different major version is to enable this option and use DNs/TTs from a 1.2.x
build and have a NN or JT from a 0.20 build.
Sounds reasonable.
> add flag to disable completely version check in the TaskTracker and DataNode
> ----------------------------------------------------------------------------
>
> 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, HADOOP-8968.patch, HADOOP-8968.patch,
> HADOOP-8968.patch, HADOOP-8968.patch
>
>
> The current logic in the TaskTracker and the DataNode to allow a relax
> version check with the JobTracker and NameNode works only if the versions of
> Hadoop are exactly the same.
> We should add a switch to disable version checking completely, to enable
> rolling upgrades between compatible versions (typically patch versions).
--
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
